Code2Prompt is a command-line tool that collects a codebase and formats it as one prompt containing source context, templates, and token information for a language model. Developers use it to prepare focused repository context for ChatGPT, Claude, coding agents, or programs that call an MCP server. The catalogue entries provide skills and an instruction for installing and using Code2Prompt to navigate repositories and gather scoped context.
Borrowing it
Nothing to install: this file belongs to mufeedvh/code2prompt. 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/mufeedvh/code2prompt/main/AGENTS.mdgit clone --depth 1 https://github.com/mufeedvh/code2promptWrote 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/mufeedvh/code2prompt/agents-md)<a href="https://agentmods.dev/instructions/mufeedvh/code2prompt/agents-md"><img src="https://agentmods.dev/badge/instructions/mufeedvh/code2prompt/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/mufeedvh/code2prompt/agents-md"><img src="https://agentmods.dev/badge/instructions/mufeedvh/code2prompt/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00299 | $0.00299 |
| Opus 5 | $0.00150 | $0.00150 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
code2prompt 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 yesterday.
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.
What it actually says
code2prompt agent guide
Project-specific skills live in .agents/skills/.
These contributor skills use metadata.internal: true to stay out of public
Skills CLI discovery. The installable user skill lives in skills/code2prompt/.
Rules
- Follow existing code2prompt patterns before generic best practices.
- Put reusable product logic in
code2prompt-core. - Keep CLI/TUI concerns in
code2prompt. - Keep Python bindings thin: delegate behavior to the core.
Code2PromptSessioncoordinates configuration, selection, and loadedSessionData.- Keep the website as a consumer of product behavior, not a second implementation.
- Prefer small changes and existing dependencies.
- Preserve public behavior unless the task explicitly changes it.
- Bug fixes should include a regression test when practical.
- Comments should explain non-obvious intent, constraints, or tradeoffs, not narrate code.
- Do not claim completion until the relevant verification skill passes.
Skills
- Implementation/refactoring →
code2prompt-conventions crates/code2prompt-core/**→verify-corecrates/code2prompt/**→verify-clicrates/code2prompt-python/**→verify-pythonwebsite/**→verify-website- Public behavior/docs/comments →
documentation
A change can require several verification skills. Root cargo test does not exercise
the Python bindings.
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.
- yesterday First seen · 32 lines · 299 tokens per session scan A b043eabc6877
code2prompt AGENTS.md is an instructions file published in the GitHub repository mufeedvh/code2prompt (7,634 stars, last pushed yesterday), licensed MIT. It adds 299 tokens to every session, about $0.0015 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-09-07.
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.