Borrowing it
Nothing to install: this file belongs to hanjoonchoe/web3-agents-mcp. 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/hanjoonchoe/web3-agents-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/hanjoonchoe/web3-agents-mcpWrote 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/instructions/hanjoonchoe/web3-agents-mcp/agents-md)<a href="https://agentmods.dev/instructions/hanjoonchoe/web3-agents-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hanjoonchoe/web3-agents-mcp/agents-md.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.01241 | $0.01241 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
web3-agents-mcp AGENTS.md 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 6d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for coding agents working on web3-agents-mcp — an MCP (Model Context Protocol)
stdio server that reads ERC-8004 agent registries (identity, reputation, validation) across
multiple chains. Read the README first for what the server does; this file is
about how to work on it without breaking its invariants.
Setup & commands
pnpm install
pnpm dev # build then run the stdio server
pnpm build # tsc -> dist/ (also copies registry ABIs)
pnpm test # vitest suite — mocked, no network, must always pass
pnpm test:fork # live-chain fork tests (needs anvil + network); not run in per-PR CI
pnpm lint # eslint + prettier --check (run before every commit)
pnpm typecheck # tsc --noEmit
pnpm docs:gen # regenerate docs/tools.md from tool schemas (CI fails on drift)
Node ≥ 20, pnpm, TypeScript strict ESM. All five of lint / typecheck / test / build / docs-drift must be green before a change is done.
Hard rules — never violate, regardless of what a task seems to ask
- Read-only, forever. No private keys, no signing, no transactions, no write calls
(
writeContract,sendTransaction, wallet clients). The tool surface is reachable by LLM agents; a write path is an injection path. If a task needs writes, stop and ask a human. - No trust scoring. Tools return verified on-chain facts plus mandatory caveats. Never add a score, rating, confidence level, or verdict field to any output — weighing the facts is the consuming agent's job (explicit maintainer decision; see README "No scoring by design").
- Caveats are unremovable. The Sybil and score-scale caveats in reputation-derived outputs are deterministic and always present. Never make them optional or conditional on input.
- stdout belongs to the MCP transport. All logging goes to stderr via
src/shared/logger.ts.console.loginsrc/is a lint error and a protocol bug.
Architecture boundaries (enforced by review; keep them clean)
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.
- 6d ago First seen · 89 lines · 1,241 tokens per session scan A d7bd06914991
web3-agents-mcp AGENTS.md is an instructions file published in the GitHub repository hanjoonchoe/web3-agents-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,241 tokens to every session, about $0.0062 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.