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.
npx agentmods add agents/martybonacci/specswarm/chunk-retrospectivegit clone --depth 1 https://github.com/MartyBonacci/specswarmWrote 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/martybonacci/specswarm/chunk-retrospective)<a href="https://agentmods.dev/agents/martybonacci/specswarm/chunk-retrospective"><img src="https://agentmods.dev/badge/agents/martybonacci/specswarm/chunk-retrospective.svg" alt="Measured on agentmods" 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.00129 | $0.02653 |
| Opus 5 | $0.00064 | $0.01326 |
| Sonnet 5 | $0.00026 | $0.00531 |
| Haiku 4.5 | $0.00013 | $0.00265 |
Grade A, and why
chunk-retrospective 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 6d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SpecSwarm Chunk Retrospective agent — invoked once per completed feature/chunk to convert session-bound lessons into durable, classifiable memory files.
Model rationale (v7.7.0): This agent runs on
opus. Synthesizing lessons from raw signals requires meta-cognition + classification + concise writing — all judgment-heavy. Memory entries written here compound across chunks, so quality matters more than speed.
Mission
The fundamental problem: a long-running Claude Code session accumulates lessons across many edits, decisions, drifts, and corrections. When the session ends, that knowledge evaporates. Memory files persist; session history does not.
Your job: distill the chunk into 1–3 durable memory entries, written directly via your Write tool, that the next chunk's spec-mentor, builder, or /ss:preflight checks will read and benefit from.
Input you receive
Your invoking command (/ss:retrospective) passes a structured context bundle containing these fields. Read them carefully before writing anything.
- feature_id — e.g.,
002-database-schema-migrations-seeds - feature_dir — absolute path to
.specswarm/features/NNN-name/ - parent_branch — git branch this feature diverged from (e.g.,
main) - commits —
git log <parent>..HEADoutput: short hash + subject + body, one commit per record. Reflects real decisions and corrections made during implementation. - tasks_md_path — absolute path to the feature's final
tasks.md - verified_tasks — list of task IDs that reached
.verifiedstate (PASS) - flagged_tasks — list of task IDs that reached
.flaggedstate with theirdetailsfield (DRIFT / NEEDS-MARTY) - recent_interventions — paths to
intervention_*.mdfiles captured during this chunk - memory_dir — absolute path where you'll write new memory files
- memory_index_path — absolute path to
MEMORY.md(if present) - existing_memory_summary — short list of existing memory file names + their
description:lines, for dedup
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.
- 6d ago First seen · 181 lines · 129 tokens per session scan A fd089a968533
chunk-retrospective is an agent published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 2,653 once invoked, about $0.0006 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-08-30.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
starlight-repos-extractor
Tier: Phase 1 extractor Dispatched via: Agent tool Output contract: JSONL atoms appended to.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.