warp-balances
Skill76 starsChanged 20 days agoApache-2.0View on GitHub
Run hyperlane warp balances to display the token balance of each leg in a warp route.
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Run hyperlane warp balances to display the token balance of each leg in a warp route.
- Very specific: line 52
If the user wants to save the output, add --out balances.json.
- Distinctive: line 54
If the user wants to filter to specific chains:
- Very specific: line 60
If the user wants to check their own token balance on each leg, add --address:
- Very specific: line 66
If the user wants raw base-unit amounts (no decimal formatting), add --raw:
- Distinctive: line 81
Sanity check after deployment: verify collateral and synthetic supplies are in sync
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Warp Route Balances
Run hyperlane warp balances to display the token balance of each leg in a warp route.
Usage
hyperlane warp balances \
--warp-route-id <SYMBOL/chains> \
--registry <path-or-url>Options
| Flag | Description |
--warp-route-id / -w | Warp route ID (e.g. ETH/ethereum-arbitrum). Prompts interactively if omitted. |
--registry / -r | Registry path or URL. Defaults to the public Hyperlane registry. |
--chains | Filter to specific chains (space-separated). |
--out / -o | Write results to a JSON or YAML file. |
--address | User address to check balances for. Shows the user's token balance on each chain instead of collateral/supply. |
--raw | Show balances in base units (without decimal formatting). |
Output columns
| Column | Description |
(index) | Chain name |
Symbol | Token symbol |
Standard | Token standard (e.g. EvmHypCollateral, EvmHypSynthetic) |
Address | Router contract address |
Balance | Collateral locked / circulating supply (default), or user's token balance (with --address) |
Instructions
- Determine the warp route ID and registry to use. If not provided, ask the user.
Run the command:
hyperlane warp balances --warp-route-id <ID> --registry <REGISTRY>- If the user wants to save the output, add
--out balances.json. If the user wants to filter to specific chains:
hyperlane warp balances --warp-route-id <ID> --registry <REGISTRY> --chains ethereum arbitrumIf the user wants to check their own token balance on each leg, add
--address:hyperlane warp balances --warp-route-id <ID> --registry <REGISTRY> --address <USER_ADDRESS>If the user wants raw base-unit amounts (no decimal formatting), add
--raw:hyperlane warp balances --warp-route-id <ID> --registry <REGISTRY> --raw- Report the balances to the user, noting:
- Without
--address: collateral legs show locked/backing balance; synthetic legs show total circulating supply - With
--address: every leg shows the user's token balance on that chain --rawapplies to all balance values and the mismatch summary (base units, no decimals)Errorin the Balance column means the RPC call failed for that leg- Without
--address: a status line is printed after the table — green if collateral == synthetic total, yellow warning with diff if they diverge
- Without
Common use cases
- Sanity check after deployment: verify collateral and synthetic supplies are in sync
- Investigate imbalance: compare collateral locked vs synthetic supply across legs
- Audit liquidity: see how much of the bridged asset is available on each chain
- Check user holdings: see how much of the token a specific address holds on each chain
Example — route liquidity
hyperlane warp balances --warp-route-id USDC/base-optimism --registry ~/hyperlane-registryWarp route balances:
┌──────────┬────────┬──────────────────────┬────────────┬────────────────┐
│ (index) │ Symbol │ Standard │ Address │ Balance │
├──────────┼────────┼──────────────────────┼────────────┼────────────────┤
│ base │ USDC │ EvmHypCollateral │ 0x5244... │ 4,231,876.12 │
│ optimism │ USDC │ EvmHypSynthetic │ 0x2DBe... │ 4,231,876.12 │
└──────────┴────────┴──────────────────────┴────────────┴────────────────┘
Status: collateral matches synthetic supply (4,231,876.12)Example — user balances
hyperlane warp balances --warp-route-id USDC/base-optimism --registry ~/hyperlane-registry --address 0xYourAddressWarp route balances for 0xYourAddress:
┌──────────┬────────┬──────────────────────┬────────────┬──────────┐
│ (index) │ Symbol │ Standard │ Address │ Balance │
├──────────┼────────┼──────────────────────┼────────────┼──────────┤
│ base │ USDC │ EvmHypCollateral │ 0x5244... │ 500.00 │
│ optimism │ USDC │ EvmHypSynthetic │ 0x2DBe... │ 250.00 │
└──────────┴────────┴──────────────────────┴────────────┴──────────┘Example — raw base units
hyperlane warp balances --warp-route-id USDC/base-optimism --registry ~/hyperlane-registry --rawWarp route balances:
┌──────────┬────────┬──────────────────────┬────────────┬───────────────┐
│ (index) │ Symbol │ Standard │ Address │ Balance │
├──────────┼────────┼──────────────────────┼────────────┼───────────────┤
│ base │ USDC │ EvmHypCollateral │ 0x5244... │ 4231876120000 │
│ optimism │ USDC │ EvmHypSynthetic │ 0x2DBe... │ 4231876120000 │
└──────────┴────────┴──────────────────────┴────────────┴───────────────┘
Status: collateral matches synthetic supply (4231876120000)In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-registry-changesetSkill
- build-docker-imageSkill
- classify-onchain-ownerSkill
- code-reviewSkill
- debug-messageSkill
- debug-rpc-providerSkill
- debug-validator-checkpoint-inconsistencySkill
- denylist-stuck-messagesSkill
- fetch-linear-ticketSkill
- fetch-safe-tx-batchSkill
- find-docker-imageSkill
- fix-merkle-root-mismatchSkill
- fix-rpc-urlsSkill
- gcp-logsSkill
- hyperlane-message-utilsSkill
- hyperlane-utilsSkill
- inline-pr-commentsSkill
- investigate-merkle-root-mismatchSkill
- investigate-stuck-messagesSkill
- registry-yaml-sort-policySkill
- security-reviewSkill
- self-relay-hyperlane-messageSkill
- set-moonpay-standing-quotesSkill
- start-http-registrySkill
- stop-http-registrySkill
- svm-warp-alt-manageSkill
- svm-warp-program-upgradeSkill
- tob-reviewSkill
- verify-warp-contractsSkill
- warp-deploy-fund-deployerSkill
- warp-deploy-init-routeSkill
- warp-deploy-nexusSkill
- warp-deploy-register-routeSkill
- warp-deploy-select-keysSkill
- warp-deploy-send-testSkill
- warp-deploy-update-ownersSkill
- warp-deploy-validate-ownersSkill
- warp-forkSkill
- warp-key-value-expansionSkill
- warp-manage-offchain-quotesSkill
- warp-route-checkSkill
- warp-run-logSkill
- warp-simulate-svm-txsSkill
- warp-update-extendSkill
- warp-update-proposeSkill
- warp-update-resolve-artifactsSkill
- warp-updateSkill
- warp-verify-onchain-configSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

