Borrowing it
Nothing to install: this file belongs to design-and-deliver/claude-code-autoconfig. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/design-and-deliver/claude-code-autoconfig/main/.claude/commands/sync-claude-md.mdgit 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/sync-claude-md)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/sync-claude-md"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/sync-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/design-and-deliver/claude-code-autoconfig/sync-claude-md"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/sync-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.00000 | $0.00528 |
| Opus 5.5 | $0.00000 | $0.00211 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
sync-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 1mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync CLAUDE.md
Verify that CLAUDE.md has the required structure. This command does NOT populate project descriptions — CLAUDE.md grows organically through Discoveries as you work. Claude can read your config files directly.
Step 1: Check for Team Feedback
Read .claude/feedback/FEEDBACK.md for any corrections or guidance from the team. Note any relevant entries.
Step 2: Verify CLAUDE.md Structure
Check that CLAUDE.md exists and has the required elements:
-
Auto-generated markers — ensure these exist:
<!-- AUTO-GENERATED BY /autoconfig at {TIMESTAMP} UTC --> ... <!-- END AUTO-GENERATED at {TIMESTAMP} UTC --> -
Team Feedback pointer — between the markers:
## Team Feedback @.claude/feedback/FEEDBACK.md FEEDBACK.md is reserved for human-authored corrections only — do not write to it. -
Discoveries section — below the end marker:
## Discoveries <!-- Claude: append project-specific learnings, gotchas, and context below. This section persists across /autoconfig runs. --> -
Flavor-package managed blocks — if CLAUDE.md contains blocks delimited by
<!-- cca-<name>:begin ... -->…<!-- cca-<name>:end -->(e.g.cca-mefrom claude-code-cad), leave them exactly as found. They are owned by flavor packages; never edit, move, or delete them, and copy them through verbatim on any rewrite.
If any of these are missing, add them. Never remove or overwrite existing content — especially the Discoveries section, which contains organic learnings from real work, and any cca- managed block.
If CLAUDE.md doesn't exist at all, create it with the minimal template from /autoconfig Step 1.
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.
- 1mo ago Changed · -1 lines 38c3b8e25eea
- 2mo ago First seen · 49 lines · 0 tokens per session scan A f112ec4c3f63
sync-claude-md is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 528 tokens. 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
context-stats
Display context window usage and token statistics.
sync
Session bootstrap - read project context, restore saved state, show status. Quick orientation with optional deep dive.
handoff
Write a session handoff document for continuity.
forge-compact-task
Compact context with dotforge-standardized hint that preserves decisions, files modified, pending TODOs, behaviors disabled, and last commit. Use at 80% context window instead of waiting for auto-compact.
checkpoint
Write a new link in the continuum chain summarizing decisions/changes since the last link.
dream
Roll up the last N links into a single phase-digest link; originals move to archived/ (never deleted).