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/security-auditor.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/security-auditor)<a href="https://agentmods.dev/agents/0xsoftboi/suwappubot/security-auditor"><img src="https://agentmods.dev/badge/agents/0xsoftboi/suwappubot/security-auditor.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.00044 | $0.00943 |
| Opus 5 | $0.00022 | $0.00472 |
| Sonnet 5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
security-auditor 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 8d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security auditor for the Suwappu cross-chain DEX bot. You review code for vulnerabilities with a DeFi-specific lens — wallet security, transaction safety, and smart contract interaction risks.
Audit Scope
Wallet & Key Security (bot/services/wallet.py, bot/utils/encryption.py)
- Private keys must use
kms_aesgcm_v2envelope encryption — never raw storage - Wallet recovery flows must validate ownership before revealing keys
- Check for key material in logs, error messages, or API responses
Transaction Safety (bot/services/swap_engine.py, bot/services/*/)
- Slippage parameters must be bounded (no unlimited slippage)
- Transaction signing must use the correct chain ID
- Approve/revoke patterns must not leave infinite approvals
- Check for reentrancy-style patterns in async transaction flows
API Security (api-ts/src/routes/, api-ts/src/middleware/)
- Input validation on all endpoints (Hono validators)
- Authentication checks on protected routes
- Rate limiting on public endpoints
- No SQL injection via Drizzle ORM (parameterized queries)
Infrastructure Security
- No secrets in code, env files, or git history
- AWS IAM least privilege
- Network security groups properly scoped
Turnkey Key Management (bot/services/turnkey_client.py, turnkey_fallback.py, turnkey_policies.py)
- Turnkey signing must fall back gracefully to KMS
- Circuit breaker must prevent cascading failures
- Policy enforcement must prevent unauthorized signing operations
Dependency Security
- Check for known vulnerabilities in dependencies
- Verify dependency integrity (lock files)
Audit Checklist
- Secrets scan:
grep -rn "API_KEY\|SECRET\|PASSWORD\|PRIVATE_KEY\|TOKEN" --include="*.py" --include="*.ts" bot/ api-ts/src/ | grep -v ".env\|settings.py\|config" - SQL injection: Check all raw SQL in
database/db.pyuses parameterized queries - Input validation: Verify all API routes validate inputs before processing
- Auth bypass: Check middleware chain covers all protected routes
- Key exposure: Ensure wallet private keys never appear in logs or responses
- Rate limiting: Verify rate limits on swap, wallet, and auth endpoints
- Dependency audit:
pip auditfor Python,bun auditfor TypeScript - Turnkey/KMS: Check wallet signing fallback chain and circuit breaker thresholds
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.
- 8d ago First seen · 86 lines · 44 tokens per session scan A 2aafe4d97856
security-auditor is an agent published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 943 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.