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 skills/drag88/claude-dev-framework/agentsmd-generatornpx skills add drag88/claude-dev-framework --skill agentsmd-generatorgit clone --depth 1 https://github.com/drag88/claude-dev-frameworkWrote 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/skills/drag88/claude-dev-framework/agentsmd-generator)<a href="https://agentmods.dev/skills/drag88/claude-dev-framework/agentsmd-generator"><img src="https://agentmods.dev/badge/skills/drag88/claude-dev-framework/agentsmd-generator.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 | $0.00020 | $0.01390 |
| Opus 5 | $0.00010 | $0.00695 |
| Sonnet 5 | $0.00004 | $0.00278 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
agentsmd-generator 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 3d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md Generator Skill
Auto-generate AGENTS.generated.md from project rules. This is the Codex / GPT-5.5 counterpart to CLAUDE.md. Also picked up by Cursor, Aider, Jules, Devin, Zed, GitHub Copilot, and other coding agents that follow the AGENTS.md convention.
When to Activate
.claude/rules/exists but noAGENTS.mdorAGENTS.generated.mdin project root- User asks "generate agents.md" or similar
- User asks "create Codex docs" or "set up AGENTS.md"
- After
/cdf:rules generatecompletes (auto-chain alongside claudemd) - After
/cdf:rules claudemdcompletes when AGENTS.md is also missing (sibling auto-chain)
What It Does
Executes the /cdf:rules agentsmd behavioral flow. The command definition in commands/rules.md is the single source of truth for:
- What gets extracted from which rule files
- Host-specific translation rules (strip
@fileimports, replace XML tags with prose, neutralize Claude-only tool names) - The output template and structure
- Line budget and guidelines
Design Principles (Codex-aligned, from rules-templates/agentsmd-codex-rulebook.md)
- Single source of truth, two host-tailored outputs. Same
.claude/rules/feeds bothCLAUDE.mdandAGENTS.md. Translate framing per host, not facts. - Target 40-60 lines. Codex caps the combined
AGENTS.mdchain at 32 KiB (project_doc_max_bytes), so root AGENTS.md stays slim and pushes per-package detail into nestedAGENTS.md. - No
@fileimports. Codex parses Markdown literally —@README.mdreads as the literal string, not a transclusion. Inline a 2-line summary if you need the content. - No
<xml_tag>blocks. XML processing tags (<plans_instruction>,<use_parallel_tool_calls>) are Claude-specific. Codex sees the angle brackets as text. - Neutral tool vocabulary. Avoid
Task tool,TeamCreate,Agent tool,subagent_type. Usesubagent,parallel investigation,host skill. - Nested
AGENTS.mdreplaces path-scoped rules. Codex does not honorpaths:frontmatter. Polyglot repos push per-package conventions into<package>/AGENTS.md. AGENTS.override.mdis the overlay convention. When a sibling agent ecosystem (Cursor, Aider) needs different framing, ship it asAGENTS.override.mdrather than forking the root file.- Every line passes: "Would removing this cause Codex to make mistakes?" If not, cut it.
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.
- 3d ago First seen · 75 lines · 20 tokens per session scan A 90cdeea15ec9
agentsmd-generator is a skill published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,390 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…