Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/greglas75/zuvonpx agentmods add skills/greglas75/zuvo/retroWrote 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/skills/greglas75/zuvo/retro)<a href="https://agentmods.dev/skills/greglas75/zuvo/retro"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/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/skills/greglas75/zuvo/retro"><img src="https://agentmods.dev/badge/skills/greglas75/zuvo/retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.07575 |
| Opus 5.5 | $0.00018 | $0.03030 |
| Sonnet 5.5 | $0.00009 | $0.01515 |
| Haiku 4.5 | $0.00004 | $0.00758 |
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 10d 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 — 588 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zuvo:retro
Generate an engineering retrospective from git history, backlog state, and skill usage trends. Produces a narrative report with actionable items.
Scope: Post-release or periodic retrospective covering shipping velocity, code churn, backlog health, and quality trends. Out of scope: Actually fixing issues (use the suggested zuvo commands in the Actionable Items section).
Argument Parsing
| Input | Action |
|---|---|
| (empty) | Auto-detect window from memory/last-ship.json or last two git tags |
<range> |
Explicit git range, e.g., v1.0.0..v1.2.0 |
--since <tag> |
Start of retrospective window (open-ended, through HEAD) |
--path <dir> |
Scope git analysis to a subdirectory (required for monorepos) |
Environment Compatibility
Dispatch follows ../../shared/includes/execution-policy.md through env-compat. Reuse existing
authorization within that policy; session restrictions take precedence. Run each required gate
and report its actual independence or an unmet requirement.
Read ../../shared/includes/env-compat.md for agent dispatch patterns, path resolution, and progress tracking across all supported platforms.
Mandatory File Loading
CORE FILES LOADED:
1. ../../shared/includes/env-compat.md -- READ
2. ../../shared/includes/run-logger.md -- READ
Both files must be read before proceeding. If either is missing, note "DEGRADED -- [file] unavailable" in the report and continue with reduced capability.
Phase 0: Window Detection
Determine the retrospective window in this priority order:
- Explicit argument — if
<range>was provided (e.g.,v1.0.0..v1.2.0), use it directly. --since <tag>— if provided, window is<tag>..HEAD. No--untilflag is defined.memory/last-ship.json— read the file if it exists. Use therangefield (SHA-based, e.g.,"abc1234..def5678"). If the artifact uses a legacy version-based range, fall back to it.- Last two git tags — run
git describe --tags --abbrev=0twice (with--excludeon first result) to derive<prev-tag>..<latest-tag>. - Fallback — if fewer than two tags exist, use the last 30 commits: derive range as
HEAD~30..HEAD.
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.
- 10d ago Changed b5b32d0dcd4a
- 18d ago Changed · +7 lines 3a7c58690355
- 20d ago Changed · +22 lines 6bc5b4131c60
- 1mo ago Changed · -2 lines e348ce7810ee
- 1mo ago First seen · 561 lines · 44 tokens per session scan A 3a7d73424921
retro is a skill published in the GitHub repository greglas75/zuvo (8 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 7,575 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
ring:dispatching-workflows
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
ring:planning-small-features
Planning the lightweight 4-gate Small Track pre-dev workflow (research, PRD, TRD, plan) with human approval and state tracking at each gate. Use for features under 2 days that reuse existing patterns and add no new dependencies, data models, or services. Skip for larger or complex features — use…