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/enable-retro.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/enable-retro)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/enable-retro"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/enable-retro.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.1 | $0.00000 | $0.00475 |
| Opus 5 | $0.00000 | $0.00237 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
enable-retro 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enable Retro
Enable the experimental Retro feature, which lets Claude log tech debt and improvement opportunities as structured story files.
What This Does
- Creates
.claude/retro/directory with a README - Verifies the shipped
.claude/agents/create-retro-item.mdagent is present (it ships with autoconfig — this command never authors it) - Adds Retro instructions to CLAUDE.md
Step 1: Create Retro Directory
Create .claude/retro/README.md with:
# Retro Items
Tech debt and improvement opportunities identified during development.
Each item is a structured story file with:
- Problem description
- Acceptance criteria
- Suggested approach
- Priority & effort sizing
- Files involved
## Working with Retro Items
- "Fix retro #001" — Work on a specific item
- "What's in the retro backlog?" — List pending items
- Items are numbered sequentially (001, 002, etc.)
Step 2: Verify Retro Agent
The agent ships with autoconfig at .claude/agents/create-retro-item.md — verify it exists. If it's missing, reinstall with npx claude-code-autoconfig (do NOT re-author it from memory; the shipped file is canonical).
Step 3: Update CLAUDE.md
Add the following section to CLAUDE.md (before Team Feedback if present):
## Retro
After completing tasks, if you encountered friction, tech debt, or improvement opportunities worth revisiting, use the create-retro-item agent to log it in `.claude/retro/`. Use your judgment on what's worth capturing — not everything needs a retro item.
Step 4: Confirm
Output: "Retro enabled. Claude will now log tech debt to .claude/retro/ when appropriate."
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 · 56 lines · 0 tokens per session scan A 6b0ea535d763
enable-retro is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 475 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
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.