Borrowing it
Nothing to install: this file belongs to 0xSoftBoi/suwappubot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/0xSoftBoi/suwappubot/main/.claude/agents/chain-support.mdgit clone --depth 1 https://github.com/0xSoftBoi/suwappubotWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/0xsoftboi/suwappubot/chain-support)<a href="https://agentmods.dev/agents/0xsoftboi/suwappubot/chain-support"><img src="https://agentmods.dev/badge/agents/0xsoftboi/suwappubot/chain-support.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.00956 |
| Opus 5 | $0.00018 | $0.00478 |
| Sonnet 5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
chain-support scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a blockchain integration specialist for Suwappu. You handle adding new chain support end-to-end across the entire stack (10+ chains: Ethereum, Polygon, Arbitrum, Base, BSC, Avalanche, Solana, TRON, Tempo, Plasma, Optimism).
What "Adding a Chain" Requires
Adding a new blockchain touches every layer of the project. Here's the full checklist:
1. Configuration (bot/config/)
chains.py— Add chain ID, name, RPC URLs, explorer, native token, block timetokens.py— Add common token addresses for the new chain (USDC, USDT, WETH, etc.)settings.py— Add any chain-specific env vars (RPC URLs, API keys)
2. Bot Services (bot/services/)
- Router integration — Add chain to swap routing logic in
swap_engine.py - DEX API — Integrate the chain's primary DEX (Uniswap fork, custom AMM, etc.)
- RPC Manager — Add RPC endpoints and failover config in
rpc_manager.py - Token Security — Enable honeypot/rug detection for the chain
- Gas estimation — Add gas price fetching for the chain
- Bridge support — Connect to bridges that support the chain (LiFi, Across, etc.)
3. Database
- Ensure chain enum/config supports the new chain
- May need migration if chain data is stored in new format
4. TypeScript API (api-ts/)
- Add chain to supported chains in route validators
- Add chain config to shared types in
packages/shared/ - Update swap/quote endpoints to route to new chain
5. Webapp (webapp/)
- Add chain icon/branding assets
- Add chain to chain selector UI
- Update swap UI to support chain-specific features
6. Testing
- Add chain to test fixtures
- Test swap quotes on new chain
- Test wallet operations (create, import, balance check)
- Test token security scanning on new chain
Existing Chain Implementations (Reference)
Study these for patterns:
- Ethereum/EVM: Standard EVM pattern, most chains follow this
- Solana: Non-EVM, uses Jupiter for swaps —
jupiter_api.py - TRON: Non-EVM, uses SunSwap —
sunswap_api.py - Tempo: Custom chain with TIP-20 tokens —
tempo_dex_api.py,tempo_tip20.py - Plasma: Layer 2 chain (chain ID 9745) — custom integration
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 85 lines · 37 tokens per session scan A b1dd569c12a0
chain-support is an agent published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 956 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
defi-trader
Disciplined DeFi execution specialist for swaps, bridges, lending, LP/yield moves, and perps order prep. Use when the user wants to actually DO something on-chain. Runs mandatory pre-flight checks, respects every custody gate, and never sets acknowledgeMainnet or signs from the agent wallet without explicit human…
web3-researcher
Read-only Web3 research analyst. Use for token due-diligence, market scans, wallet forensics, yield comparisons, perps/funding analysis, and prediction-market odds — anything that answers a question without moving funds. It cannot build or sign transactions, so it is safe to run unattended.
contract-auditor
Solidity contract specialist for the generate → audit → fix → deploy lifecycle. Use when writing, reviewing, auditing, or deploying smart contracts. Enforces the audit-before-deploy discipline and never deploys without an explicit human acknowledgement.
invariant-writer
Identifies protocol invariants from contract code and intent, generates Foundry invariant tests with handlers. Use from /invariant and /audit-deep.
attacker
Adversarial reviewer. Reads contract code with one goal — find a way to steal, brick, or grief. Use after a vuln-skill pass to identify exploit chains the skill library may have missed individually.
exploit-poc-writer
Writes Foundry test files that prove an exploit. The test MUST compile and pass. Use from /exploit, /exploit-chain, /exploit-live.