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/design-and-deliver/claude-code-autoconfig/extract-rulesgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWrote 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/commands/design-and-deliver/claude-code-autoconfig/extract-rules)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/extract-rules"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/extract-rules.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.00000 | $0.02916 |
| Opus 5 | $0.00000 | $0.01458 |
| Sonnet 5 | $0.00000 | $0.00583 |
| Haiku 4.5 | $0.00000 | $0.00292 |
Grade B, and why
extract-rules scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
5. Auto memory files — memory often contains misplaced imperatives that should be promoted to rules. To find the memory directory, list `~/.claude/projects/` and fuzzy-match against the current project path. The director How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract Rules
Scan all Claude configuration artifacts and propose structured rules for .claude/rules/.
Step 0: Git safety check
Before doing anything else, check for uncommitted changes:
git status --porcelain
If there are uncommitted changes, show this warning and wait for confirmation:
Warning: This command will modify files (extract rules from sources and optionally clean up originals). You have uncommitted changes.
Commit your work before proceeding, or type "continue" to proceed anyway.
If the working tree is clean, proceed silently.
Step 1: Discover sources
Scan these locations for .md files containing potential rules. Skip any that don't exist — not all projects have all of these:
CLAUDE.md(project root)CLAUDE.local.md(project root, if present)- All
.mdfiles in.claude/recursively (feedback, commands, etc.) — excluding.claude/rules/and.claude/commands/extract-rules.md - Any nested
CLAUDE.mdfiles in subdirectories (e.g.,src/CLAUDE.md) - Auto memory files — memory often contains misplaced imperatives that should be promoted to rules. To find the memory directory, list
~/.claude/projects/and fuzzy-match against the current project path. The directory name encodes the path with dashes replacing separators, but encoding varies by platform and may not be consistent for paths with spaces, special characters, or deep nesting. Discovery strategy: list all directories under~/.claude/projects/, then find the one whose name best matches the current working directory (check if the directory name contains key path segments like the project folder name). ReadMEMORY.mdin that directory, then each.mdfile it links to. If no match is found or the memory directory can't be read, skip this source silently.
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.
- 5d ago First seen · 261 lines · 0 tokens per session scan B 6ea40c27884d
extract-rules is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,916 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.