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/agents/create-retro-item.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/agents/design-and-deliver/claude-code-autoconfig/create-retro-item)<a href="https://agentmods.dev/agents/design-and-deliver/claude-code-autoconfig/create-retro-item"><img src="https://agentmods.dev/badge/agents/design-and-deliver/claude-code-autoconfig/create-retro-item.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.00363 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
create-retro-item 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 2d 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.
What it actually says
Create Retro Item Agent
Create a fully-scoped story file in .claude/retro/ when tech debt or improvement opportunities are identified.
When to Trigger
Call this agent when you notice:
- Tech debt that should be addressed later
- Code that works but could be improved
- Missing tests, documentation, or error handling
- Architectural improvements worth tracking
Input
Provide these details when calling:
- title: Short descriptive name (used for filename)
- problem: What's wrong or what friction was encountered
- criteria: Specific, testable acceptance criteria
- approach: How to fix it
- priority: Critical | High | Medium | Low
- effort: S | M | L | XL
- files: List of files involved
Behavior
- Generate filename from title:
kebab-case.md - Create story file in
.claude/retro/using this format:
# [Title]
## Problem
[Problem description]
## Acceptance Criteria
- [ ] [Criteria 1]
- [ ] [Criteria 2]
## Approach
[How to fix]
## Priority
[Priority level]
## Effort
[Effort size]
## Files
- [file1]
- [file2]
- Confirm creation with filename
Guidelines
- Be concise: Keep descriptions actionable, not verbose
- Be specific: Include actual file paths and line numbers when relevant
- Don't duplicate: Check if similar item already exists first
- Don't block: Create the item and continue with the main task
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.
- 2d ago First seen · 63 lines · 0 tokens per session scan A 69ab5a688062
create-retro-item is an agent 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 363 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-09-05.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…