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.
npx agentmods add instructions/radareorg/radare2-mcp/agents-mdgit clone --depth 1 https://github.com/radareorg/radare2-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/radareorg/radare2-mcp/agents-md)<a href="https://agentmods.dev/instructions/radareorg/radare2-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/radareorg/radare2-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.01097 | $0.01097 |
| Opus 5 | $0.00549 | $0.00549 |
| Sonnet 5 | $0.00219 | $0.00219 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
radare2-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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Coding Guidelines for r2mcp
MCP server for radare2. Source lives in src/. Files named *.inc.c are #included into other .c files — they are not separate compilation units.
Build & Test
make -j— fast incremental build (from repo root)make asan— AddressSanitizer buildmake fmt— auto-format withclang-format-radare2src/r2mcp -h— CLI helpsrc/r2mcp -t— list available toolssrc/r2mcp -T 'open_file file_path="/bin/ls"; list_functions; close_file'— run DSL testsmake test— run test suite (test.sh,test2.sh)
Code Style
- Tabs for indentation
- Space before parens:
foo (),if (,for ( - Always use braces
{}even for single-statement blocks - Declare loop variables before
for(C89 style) - Declare local variables and assign in the same line if possible
- Prefer
!strcmp ()overstrcmp () == 0 - Prefer
r_str_startswith ()over!strncmp () - Use
R_STR_ISEMPTY()/R_STR_ISNOTEMPTY()instead of manual null+empty checks - Use
R_RETURN_VAL_IF_FAIL()/R_RETURN_IF_FAIL()for preconditions inR_APIfunctions - Use
R_LOG_ERROR(),R_LOG_WARN(),R_LOG_INFO()for diagnostics
Memory
R_NEW()/R_NEW0()— assumed never to return NULLR_FREE(ptr)— frees and sets to NULL- No NULL-check before
free()or*_free()helpers r_str_newf()for formatted string allocation (not manual malloc+snprintf)RStrBuffor building strings in loops:RStrBuf *sb = r_strbuf_new (""); r_strbuf_appendf (sb, "...", ...); return r_strbuf_drain (sb); // caller freesr_json_parse()does NOT own the input buffer — caller must free it separately afterr_json_free()
JSON (PJ API)
Build JSON responses with the pj_* helpers:
PJ *pj = pj_new ();
pj_o (pj); // open object
pj_ks (pj, "type", "text"); // key-string
pj_ki (pj, "count", 5); // key-int
pj_kb (pj, "ok", true); // key-bool
pj_k (pj, "items"); pj_a (pj); /* ... */ pj_end (pj); // key + array
pj_end (pj); // close object
return pj_drain (pj); // extract string, free builder
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 · 92 lines · 1,097 tokens per session scan A fa694a822902
radare2-mcp AGENTS.md is an instructions file published in the GitHub repository radareorg/radare2-mcp (303 stars, last pushed 4d ago), licensed MIT. It adds 1,097 tokens to every session, about $0.0055 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 instructions, from other repositories
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).
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.
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.
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.
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).