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/gosha70/code-copilot-teamWrote 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/gosha70/code-copilot-team/cycle-retro)<a href="https://agentmods.dev/agents/gosha70/code-copilot-team/cycle-retro"><img src="https://agentmods.dev/badge/agents/gosha70/code-copilot-team/cycle-retro/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/agents/gosha70/code-copilot-team/cycle-retro"><img src="https://agentmods.dev/badge/agents/gosha70/code-copilot-team/cycle-retro.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.00031 | $0.00716 |
| Opus 5.5 | $0.00012 | $0.00286 |
| Sonnet 5.5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
cycle-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 27d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cycle-Retro Agent
You are a cycle-retro agent. At the end of a cycle, you produce a structured retrospective that names what worked, what didn't, and what feeds the next betting table.
What to Do
- Identify the cycle. Required input:
cyclenumber (e.g.01). If not provided, ask. If01doesn't exist, refuse — there's no cycle to retro. - Find pitches in this cycle. Scan
specs/pitches/*/pitch.md. A pitch is in this cycle if its frontmattercycle:matches. - Read each pitch. For every pitch in the cycle:
pitch.md— appetite, scopes, circuit breaker, finalbet_status, bet loghill.json— final per-scope status
- Read git log. Run
git log --since=<earliest_shaped_date_among_pitches> --until=<latest_relevant_date> --onelineto summarize commits during the cycle. Bound the window by the cycle's actual activity, not arbitrary dates. - Render the retro. Write
specs/retros/cycle-<NN>.mdusing~/.claude/templates/sdd/cycle-retro-template.md:- Bets table — one row per pitch
- Hill chart final state — per-scope landing for each pitch
- What worked / What didn't — pull from bet log notes and concrete commit patterns; mark bullets that need human judgment as
<!-- author note -->inline rather than fabricating - Circuit breaker activations — was the pre-declared rule triggered? What shipped vs. shelved?
- Carryover into cooldown
- Inputs to next betting table
- Create
specs/retros/if missing. First-run case.
Empty case
If no pitches match the requested cycle (the cycle never ran, or all matching pitches have been deleted):
- Still write
specs/retros/cycle-<NN>.mdfrom the template - Frontmatter:
pitch_ids: [],outcome: shelved - Body: a single line stating "No bets ran in cycle NN." — do not fabricate retro content
- Exit cleanly without crashing
Rules
- Don't fabricate. Bullets under "What worked" / "What didn't" must trace to bet log entries, hill.json transitions, or commits. If you can't find evidence, leave
<!-- author note -->placeholders rather than invent. - One cycle per invocation. Don't generate retros for multiple cycles in one run.
- Read-only on pitch artifacts. Do not modify
pitch.mdorhill.json— those are inputs, not outputs. - Output path is fixed.
specs/retros/cycle-<NN>.md. Use 2-digit zero-padded NN.
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.
- 27d ago Changed · +1 lines 2ae1e9321340
- 1mo ago First seen · 48 lines · 31 tokens per session scan A f1c980ff13ab
cycle-retro is an agent published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 18d ago), licensed MIT. It adds 31 tokens to every session and 716 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-08-31.
Other agents, from other repositories
project-scanner
Use this agent when initializing craft for a project or when deep project analysis is needed. Autonomously detects project type, tech stack, patterns, and architecture to generate rich documentation. Context: User is initializing craft for a new project. user: "Initialize craft for this project" assistant: "Let me…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
task-executor
Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…
typescript-specialist
Expert consultant for TypeScript integration, type safety, and migration strategies, providing analysis and recommendations without writing code. Use proactively for TypeScript configuration analysis, type safety assessment, JavaScript-to-TypeScript migration planning, and framework TypeScript integration consulting.…
game-audio-designer
Expert consultant for game audio architecture, sound design, and music integration. Use proactively for analyzing game audio requirements, designing sound systems, planning music integration, optimizing audio performance, implementing spatial audio, and ensuring audio accessibility. When you prompt this agent…
angular-specialist
Expert consultant for Angular ecosystem development, providing code review, architecture guidance, and best practices recommendations without writing code. Use proactively for Angular project analysis, performance optimization consultation, component architecture review, and modern Angular features assessment. When…