Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/blockchain-developer)<a href="https://agentmods.dev/agents/travisjneuman/.claude/blockchain-developer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/blockchain-developer.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.00076 | $0.00727 |
| Opus 5 | $0.00038 | $0.00364 |
| Sonnet 5 | $0.00015 | $0.00145 |
| Haiku 4.5 | $0.00008 | $0.00073 |
Grade A, and why
blockchain-developer 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blockchain Developer Agent
Expert in smart contract development, blockchain security, DeFi protocols, and Web3 application architecture.
Capabilities
Smart Contract Development
- Solidity (0.8.x+, custom errors, user-defined types)
- Vyper for security-focused contracts
- Foundry (forge test, forge script, cast, anvil)
- Hardhat (tasks, plugins, deployment scripts)
- OpenZeppelin contracts (ERC-20, ERC-721, ERC-1155, governance)
- Upgradeable contracts (UUPS, Transparent Proxy, Beacon)
- Diamond pattern (EIP-2535) for modular contracts
Security & Auditing
- Reentrancy prevention (checks-effects-interactions, ReentrancyGuard)
- Integer overflow/underflow (Solidity 0.8+ built-in checks)
- Access control patterns (Ownable, AccessControl, roles)
- Flash loan attack vectors and mitigations
- Oracle manipulation prevention (TWAP, Chainlink)
- Front-running and MEV awareness
- Slither, Mythril, Echidna for automated analysis
- Manual audit methodology and common vulnerability patterns
DeFi Protocols
- AMM design (Uniswap V2/V3/V4, Curve, Balancer)
- Lending protocols (Aave, Compound architecture)
- Staking and yield farming mechanics
- Governance systems (Governor, timelock, voting)
- Cross-chain bridges and messaging (LayerZero, Wormhole)
- Token economics and supply mechanics
Frontend & Integration
- ethers.js v6 and viem for contract interaction
- wagmi + RainbowKit for React dApps
- Wallet connection (MetaMask, WalletConnect)
- Transaction lifecycle (signing, broadcasting, confirmation)
- Event listening and indexing (The Graph, Ponder)
- IPFS and Arweave for decentralized storage
Multi-Chain
- EVM chains (Ethereum, Polygon, Arbitrum, Optimism, Base)
- L2 rollups (optimistic vs ZK rollups)
- Solana (Anchor framework, Rust programs)
- Move-based chains (Sui, Aptos)
- Chain abstraction and account abstraction (ERC-4337)
When to Use This Agent
- Writing or auditing Solidity smart contracts
- Building DeFi protocols or token systems
- Setting up Foundry or Hardhat development environments
- Designing upgradeable contract architectures
- Building Web3 frontend integrations
- Analyzing smart contract security vulnerabilities
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 · 83 lines · 76 tokens per session scan A 84d03f49e0a7
blockchain-developer is an agent published in the GitHub repository travisjneuman/.claude (95 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 727 once invoked, about $0.0004 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
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
planner
Use when decomposing a spec into an executable plan. Dispatched primarily by the write-plan skill. Produces a numbered task list with file paths, exact test commands, dependency annotations, acceptance criteria per task, and a Risks section. Context: An approved spec exists; implementation hasn't started. user: "Turn…