Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add navapbc/digital-service-orchestra/plugin install dsoWrote 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/navapbc/digital-service-orchestra/retro)<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/retro"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/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/navapbc/digital-service-orchestra/retro"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/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.00183 | $0.04856 |
| Opus 5 | $0.00092 | $0.02428 |
| Sonnet 5 | $0.00037 | $0.00971 |
| Haiku 4.5 | $0.00018 | $0.00486 |
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 8d 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Retrospective
Proactive project health assessment focused on maintainability, workflow efficiency, and technical debt. Analyzes metrics, identifies improvements, and creates a structured remediation plan.
Supports dryrun mode. Use /dso:dryrun /dso:retro to preview without changes.
Usage
/dso:retro # Run full retrospective assessment
Phases
Flow: P1 (Health Assessment) → P2 (Codebase Review) → P3 (Findings Report)
→ [user approves scope] P4 (Epic Creation) → P5 (Quick Wins) → Complete
→ [user declines] End
Phase A: Health Assessment (/dso:retro)
Run the data-collection script to gather all metrics in one pass:
.claude/scripts/dso retro-gather.sh
Use --quick to skip slow checks (dependency freshness, plugin versions) when session usage is high.
The script outputs structured sections (=== SECTION_NAME ===) covering:
cleanup, validation, ticket health/stats/open/blocked/orphaned, worktree staleness,
outdated dependencies, session usage, hook error logs, timeout logs, plugin versions,
test metrics, code metrics (including TODO-family comment scan), known issues counts,
and CI shift-left data (recent run outcomes, failure rate, failed job names).
Post-Collection Analysis
After reviewing the script output:
- Error log triage: For each unique error pattern in
HOOK_ERROR_LOG, propose a ticket bug. Use AskUserQuestion to confirm which warrant creation. After triage, truncate the logs. - Plugin updates: For any outdated plugins, never recommend
@latesttags — always recommend specific pinned versions. Add as P3 cleanup items. - Friction Suggestions: If the output contains a
SUGGESTION_DATAsection, review the frequency-ranked clusters. Each cluster represents a recurring workflow friction point captured bysuggestion-record.sh. For each cluster:- Note the
file,pattern, andproposed_editfields. - Clusters with
count >= 3are high-signal and should become P2 improvement tasks. - Clusters with
count < 3are low-signal and can be grouped into a single P3 cleanup task. - If no
SUGGESTION_DATAsection is present, skip this step.
- Note the
- Report the structured health inventory (validation status, ticket health, worktree count, dependency freshness, session usage, error triage summary, plugin versions, friction suggestion summary).
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 332 lines · 183 tokens per session scan A 12549377c78f
retro is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed today), licensed Apache-2.0. It adds 183 tokens to every session and 4,856 once invoked, about $0.0009 per session on Opus 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.