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/commands/gosha70/code-copilot-team/retro)<a href="https://agentmods.dev/commands/gosha70/code-copilot-team/retro"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/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/commands/gosha70/code-copilot-team/retro"><img src="https://agentmods.dev/badge/commands/gosha70/code-copilot-team/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.00000 | $0.00389 |
| Opus 5.5 | $0.00000 | $0.00156 |
| Sonnet 5.5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
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 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.
What it actually says
Post-Session Retrospective
Run a structured retrospective for the current session. Proposes rule and documentation changes but does not apply them.
Steps
1. Session Summary
- Run
git log --oneline -20andgit diff --statto see what changed - Summarize: what was the goal? What was delivered?
- Note any gap between intent and outcome
2. Struggle Identification
Build a table of struggles encountered during this session:
| Struggle | Time Lost | Root Cause | Category |
|---|---|---|---|
| {description} | {estimate} | {what was missing or wrong} | {underspec / tooling / convention / context loss} |
Categories:
- underspec — requirement was ambiguous or incomplete
- tooling — tool limitation or misconfiguration
- convention — rule missing or unclear
- context loss — agent forgot or lost track of earlier decisions
3. Rule/Doc Gap Analysis
For each struggle, propose a specific fix:
| Struggle | Proposed Fix | Target File |
|---|---|---|
| {from table above} | {concrete change} | {path in shared/skills/, shared/templates/, or adapters/} |
Be specific: "Add rule X to file Y" not "improve documentation."
4. What Worked Well
- List patterns, rules, or workflows that prevented problems
- Identify agent configurations that were effective
- Note any conventions that saved time
5. Output
Write the retrospective to doc_internal/retro-{YYYY-MM-DD}.md (ask the user before writing).
Include all 4 sections above plus a summary of proposed changes.
Important: This command proposes rule changes but does not apply them. The user decides which proposals to implement.
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 First seen · 50 lines · 0 tokens per session scan A d9efd7bf89f2
retro is a command published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 389 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
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
story-continue
Resume an interrupted story from where you left off.
prp-prd
Interactive PRD generator - problem-first, hypothesis-driven product spec with back-and-forth questioning.
sdd
A command that creates three connected planning files for a software feature: requirements, design, and tasks.
project
Manage projects inside a topic wiki. Projects are folders under output/projects/ that group related outputs (playbooks, images, code, data) with a goal captured in WHY.md.
traceability-gen
A command that rebuilds a Markdown table linking requirements to project plans and tests. It reads requirement files, plan files, and test markers, then records what is planned or covered.