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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/standardize-claude-md)<a href="https://agentmods.dev/commands/travisjneuman/.claude/standardize-claude-md"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/standardize-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/travisjneuman/.claude/standardize-claude-md"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/standardize-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.00018 | $0.00809 |
| Opus 5.5 | $0.00007 | $0.00324 |
| Sonnet 5.5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
standardize-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 25d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standardize CLAUDE.md
Adds missing sections to an existing CLAUDE.md file while preserving project-specific content.
When to Use
- After running Claude Code's
/initon a new codebase - When inheriting a project without toolkit integration
- To retrofit older projects with the standardized pattern
Execution Flow
Step 1: Verify CLAUDE.md Exists
[ -f "./CLAUDE.md" ] && echo "EXISTS" || echo "NOT_EXISTS"
If NOT_EXISTS: Stop and suggest running /init-project instead.
Step 2: Check for Missing Sections
Read the current ./CLAUDE.md and check for:
| Section | Pattern to Find |
|---|---|
| Global delegation | Global rules from \~/.claude/`` |
| Related Global Rules | ## Related Global Rules |
| Quick Start | ## Quick Start |
| Footer | loaded from \~/.claude/`` |
Step 3: Detect Stack (if not provided)
If {{stack}} not provided, detect from:
package.json→ react or nextjspyproject.toml/requirements.txt→ pythonindex.htmlonly → static- Otherwise → ask user
Step 4: Add Missing Sections
If missing global delegation: Add after the first heading:
> **Global rules from `~/.claude/` apply automatically.**
If missing Related Global Rules: Add before Quick Start (or at end):
---
## Related Global Rules
Load these `~/.claude/` files when relevant:
- `docs/reference/stacks/[stack].md` for [stack] patterns
- `docs/reference/checklists/[checklist].md` for [checklist] work
If missing Quick Start: Add at end (before footer):
---
## Quick Start
| I want to... | Command |
| -------------------- | ---------------------------- |
| Start any task | `/start-task [description]` |
| Debug an issue | `Skill(debug-systematic)` |
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.
- 25d ago Changed · -1 lines 3d291899c3f3
- 27d ago Changed aa51c9039461
- 1mo ago First seen · 155 lines · 18 tokens per session scan A e3e0a9bf1d3b
standardize-claude-md is a command published in the GitHub repository travisjneuman/.claude (106 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 809 once invoked, about $0.0001 per session on Opus 5.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-03.
Other commands, from other repositories
ops-monitoring
Code instrumentation for monitoring/logging/alerting and deploying the observability stack.
dev-error-handling
Implements a robust and consistent error handling strategy.
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.