Agent skill · bankrbot
harness-capu
Fund OpenCAP inference from Capminal with staked CAPU on Base. Buy or mint CAPU, stake it for daily inference credit, create a wallet-owned OpenCAP API key through Ethereum sign-in, check quota, and recover or rotate the key. Use when the user wants CAPU-funded AI compute or OpenCAP key setup; Capminal trading-wallet credentials and Harness account management are separate workflows.
What it needs
About 10k tokens when loaded.
What this skill does
Capu / OpenCAP inference Stake CAPU to fund OpenCAP inference, then create a key for the wallet that owns the stake. The documented allocation is $1 of inference per staked CAPU per day, renewed at 00:00 UTC, with no rollover. Unstaked CAPU does not earn credit. This is inference capacity, not withdrawable dollars. Buying CAPU directly and staking it is the short setup path. CAP → sCAP → CAPU minting is optional; do not add a CAP purchase or sCAP stake just to create a key. No sCAP key-creation prerequisite is stated in OpenCAP's docs. Read references/opencap-api.md when signing in, creating or managing keys, or reading quota. It contains the exact dashboard request shapes and their verification status. Before any transaction, read references/transaction-safety.md and references/contracts.md, including the deployment review requirement. The contract reference also covers CAP minting and exits. Required safety gates Before signing SIWE, show the exact complete message and explain its account-management authority; require fresh explicit user confirmation. Before any swap, approval, stake, mint, unstake, burn, or transfer, build and validate the exact ordered transaction batch, show its decoded preview, and require fresh explicit user confirmation of that batch. An earlier setup request, purchase budget, or wallet connection is not final confirmation. Changes to the message or batch require a new preview and confirmation. Execute only on Base, chain ID 8453, after the transaction and reviewed deployment checks in the references pass. Stop on validation failures or scanner errors, including untrustedaddress; Flow F cannot bypass them. Before acquiring CAP/CAPU or staking, disclose that these are speculative tokens and funds can be lost. Explain token price and liquidity risk, slippage, upgradeable-contract/admin risk, smart-contract failure, withdrawal cooldowns, and gateway-credit risk (indexing delays, availability, and changing allocations). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills bankrbot/harness-capu