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.
git clone --depth 1 https://github.com/acaprino/daodanWrote 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/acaprino/daodan/create-claude-md)<a href="https://agentmods.dev/commands/acaprino/daodan/create-claude-md"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/create-claude-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/commands/acaprino/daodan/create-claude-md"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/create-claude-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.00073 | $0.01877 |
| Opus 5 | $0.00036 | $0.00938 |
| Sonnet 5 | $0.00015 | $0.00375 |
| Haiku 4.5 | $0.00007 | $0.00188 |
Grade A, and why
create-claude-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 7d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create CLAUDE.md File
This command launches an interactive session to create a new CLAUDE.md file perfectly tailored to your project and preferences.
Pre-flight: detect existing X-ray output
Before the agent starts its own bottom-up analysis, check whether the project already has technical-reference output on disk from a previous /codebase-xray:analyze session:
ls .codebase-xray/01-structure.md .codebase-xray/02-interfaces.md 2>/dev/null
If both files exist, prompt the user:
Found .codebase-xray/ from a previous /codebase-xray:analyze session.
Available technical references:
- 01-structure.md (file inventory, dependency graph, entry points, naming conventions)
- 02-interfaces.md (public APIs, contracts, "How to Add a New Module")
- 05-risks.md [if present] (anti-patterns, red flags, tech debt)
- 03-flows.md / 04-semantics.md / 07-final-report.md [if --depth=full was used]
Use these as the technical source for CLAUDE.md? You'll still answer the
workflow/preferences questions interactively.
[Y] Use X-ray output (faster, claims already verified)
[n] Re-analyze bottom-up (full discovery from scratch)
If the user accepts, the spawned claude-md-auditor agent skips Phase 1 (Bottom-Up Discovery) and ingests .codebase-xray/01-structure.md and .codebase-xray/02-interfaces.md as ground truth, with 3-5 spot-checks against current code to confirm freshness. See the agent's "Phase 0: X-Ray Detection" section for the full protocol.
If the user declines (or .codebase-xray/ is absent), the agent does its own bottom-up analysis as in step 1 below.
What This Does
The agent will:
- Analyze your project bottom-up (dependencies, entry points, source, config, tests, docs) -- OR ingest
.codebase-xray/if the pre-flight check accepted that shortcut - Ask you questions about your workflow and preferences
- Clarify any ambiguous patterns found in the codebase
- Generate a concise, accurate
CLAUDE.mdfollowing best practices - Detect whether the project has a test suite and, if so, offer the canonical
## Test-Suite Rulesblock (on by default) - Verify all claims against your actual codebase
- Review the draft with you before finalizing
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.
- 7d ago First seen · 129 lines · 73 tokens per session scan A 9c176a7a81b4
create-claude-md is a command published in the GitHub repository acaprino/daodan (9 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,877 once invoked, about $0.0004 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-05.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.