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/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/prototype-retrospective-analyst)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/prototype-retrospective-analyst"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/prototype-retrospective-analyst/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/attilaszasz/sdd-pilot/prototype-retrospective-analyst"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/prototype-retrospective-analyst.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.00024 | $0.00525 |
| Opus 5 | $0.00012 | $0.00262 |
| Sonnet 5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
Prototype Retrospective Analyst 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 7d 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
Task
Archive the completed implementation as a throwaway prototype and regenerate all canonical bootstrap artifacts from scratch, informed by everything learned.
Rules
- Project-bootstrap scope only; ignore feature-level implementation work.
- Read local repo/docs first.
- Present retrospective findings for user review before regenerating.
- Exclude all secret/credential files (e.g.,
.env) from the archive. - Recreate clean specs, ADR, and plan directories.
- Delegate sub-tasks to ADR Author, Technical Researcher, or Configuration Auditor as requested by nested workflows.
- Report progress with
todo. - Follow
.github/sddp/workflows/prototype-regen/WORKFLOW.md.
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.
- 7d ago Changed 50bbd25b8132
- 9d ago First seen · 44 lines · 24 tokens per session scan A a44c27ac8d82
Prototype Retrospective Analyst is an agent published in the GitHub repository attilaszasz/sdd-pilot (96 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 525 once invoked, about $0.0001 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 agents, from other repositories
Spec-Driven
Use this planner when the user wants implementation to be specified and approved before code changes. Select the brief lane by default for bounded work or the full requirements -> design -> tasks lifecycle for high-risk work. Never implement before the selected lane's approval gate.
sharp-edges-analyzer
Evaluates APIs, configurations, and library interfaces for misuse resistance and footgun potential. Use when reviewing code for error-prone designs, dangerous defaults, or APIs that make security mistakes easy.
sdd-scout
Architecture scout used only by /sdd-architecture-scan. Analyzes one worklist unit and writes its report to .sdd-scan/reports/. Not for general tasks.
angular-implementer
Phase 4 (green/refactor/simplify) — minimum Angular production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
angular-architect
Phase 3 — design the Angular feature, decompose into TDD-shaped frontend tasks, write ADRs. Use when the user asks for design, plan, or runs /plan for a feature touching the Angular UI.
validator
The ONE anchored agent — the independent evidence author (writes nothing into the working tree, not even via Bash): re-verifies every criterion of ONE gate against the pinned snapshot, grounds evidence in executed commands wherever possible, and writes the proof via the anchored CLI (evidence flips a criterion done…