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 commands/drag88/claude-dev-framework/rulesgit clone --depth 1 https://github.com/drag88/claude-dev-frameworkWhat 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.00021 | $0.09078 |
| Opus 5 | $0.00010 | $0.04539 |
| Sonnet 5 | $0.00004 | $0.01816 |
| Haiku 4.5 | $0.00002 | $0.00908 |
Grade A, and why
rules 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.
How it starts
The opening of the file, as written. The whole thing — 736 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cdf:rules - Project Rules Management
Generate and manage project rules in
.claude/rules/,CLAUDE.md(Claude Code), andAGENTS.md(Codex and other coding agents).
Quick Start
# No subcommand — full chain: status → generate (if missing) → claudemd + agentsmd
/cdf:rules
# Generate full rules + both host instruction files from codebase analysis
/cdf:rules generate
# Generate CLAUDE.md (Claude Code, current models) from existing rules
/cdf:rules claudemd
# Generate AGENTS.md (Codex / GPT-5.5 and 20+ other agents) from existing rules
/cdf:rules agentsmd
# Check if rules need refresh
/cdf:rules status
Default Behavior (No Subcommand)
When invoked as bare /cdf:rules with no argument, run the full chain in order:
- Inspect state: check whether
.claude/rules/and at least one rule file exist. - Generate rules if missing: if
.claude/rules/is empty or absent, run thegeneratesubcommand first. - Generate CLAUDE.md if missing: if neither
CLAUDE.mdnorCLAUDE.generated.mdexists in the project root, run theclaudemdsubcommand. - Generate AGENTS.md if missing: if neither
AGENTS.mdnorAGENTS.generated.mdexists in the project root, run theagentsmdsubcommand. - Report: tell the user exactly which files were created or skipped (and why each was skipped).
This default is the safety net for the most common ask ("set up rules for this repo"). Never stop after CLAUDE.md without also writing AGENTS.md — both host files come from the same .claude/rules/ source and must stay in sync.
When to Use
Use /cdf:rules when:
- Setting up a new project (generate initial rules)
- After major refactors (refresh rules to match new architecture)
- Rules are outdated (regenerate to match current code)
- Need
CLAUDE.md(Claude Code) orAGENTS.md(Codex) for quick reference - Working in a repo that targets both Claude Code and Codex — both files stay in sync from one source
Don't use this command for: Dev documentation or task planning (use /cdf:docs plan instead).
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 · 736 lines · 21 tokens per session scan A 85dda2503ba0
rules is a command published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 9,078 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.