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.00829 |
| Opus 5 | $0.00009 | $0.00415 |
| Sonnet 5 | $0.00004 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
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 8d 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 — 155 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]` |
| Check project status | `/gsd:progress` |
| Debug an issue | `Skill(debug-like-expert)` |
| Make a decision | `/consider:first-principles` |
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.
- 8d 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 (97 stars, last pushed 7d ago), licensed MIT. It adds 18 tokens to every session and 829 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-09-03.
Other commands, from other repositories
api-gen
Generate REST API endpoints with routes, validation, error handling, and tests.
component-gen
Generate React or Vue components with prop types, styling, accessibility, and tests.
performance-audit
Find performance bottlenecks across the stack — queries, rendering, bundle size, memory.
debug
Systematic debugging — reproduce, isolate, fix, verify, and add regression test.
doc-gen
Generate documentation — JSDoc, docstrings, README sections, or API docs.
migrate
Migrate between framework versions or languages with an audited step-by-step plan.