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 skills add voxpelli/claude-beads --skill retrospectivegit clone --depth 1 https://github.com/voxpelli/claude-beadsWrote 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/voxpelli/claude-beads/retrospective)<a href="https://agentmods.dev/skills/voxpelli/claude-beads/retrospective"><img src="https://agentmods.dev/badge/skills/voxpelli/claude-beads/retrospective/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/voxpelli/claude-beads/retrospective"><img src="https://agentmods.dev/badge/skills/voxpelli/claude-beads/retrospective.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.00091 | $0.05005 |
| Opus 5 | $0.00046 | $0.02502 |
| Sonnet 5 | $0.00018 | $0.01001 |
| Haiku 4.5 | $0.00009 | $0.00500 |
Grade A, and why
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 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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Retrospective
Generate a sprint retrospective for this project. If the project CLAUDE.md has
a Sprint retrospectives section with a template, use it; otherwise use the
template below.
Context
Retrospective files are named RETRO-NN.md in the project root. Each covers one
sprint's worth of work.
Workflow
Beads availability
Beads is available iff a .beads/ directory exists and command -v bd
succeeds; this component is Tier C per CLAUDE.md
### Beads-availability convention. Steps 1–3 and the UPSTREAM / SYNERGY /
Basic Memory parts of the trend review are beads-independent and run unchanged.
When beads is unavailable, the three bd-dependent steps degrade and
announce (never skip silently):
- Health audit (step 4) — replace the
bdhealth checks with an announced skip line in the RETRO### Health auditsubsection (see step 4). - Findings (step 5) — append a
### Follow-ups (untracked)task list to the RETRO file instead of runningbd create(see step 5). - Decision capture (step 5) — record decisions inline as a
### Decisionsblock in the RETRO file instead ofbd create --type=decision(see step 5).
1. Determine sprint number
ls RETRO-*.md | sort -V | tail -1
Extract the highest sprint number and increment by 1.
This file count is canonical for the trend-review heuristic in step 4 —
do not substitute a user-asserted topic number, release number, or bd
sprint label. If RETRO-NN.md count is divisible by 4, this IS a
trend-review sprint regardless of how the work is verbally framed.
2. Gather context
Run these in parallel:
Recent commits since last retro:
# Anchor to the commit that created/last modified the previous RETRO file.
# Edge cases that both result in full-history range (correct for Sprint 1):
# 1. No prior RETRO-*.md files exist yet
# 2. RETRO files are gitignored — git log -- RETRO-*.md returns empty
# In both cases the inner git log returns empty, making the range "..HEAD"
# which shows all commits — the right behavior for a first retrospective.
git log --oneline "$(git log -1 --format=%H -- RETRO-*.md)"..HEAD --no-merges
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 First seen · 451 lines · 91 tokens per session scan A 19049fad59f2
retrospective is a skill published in the GitHub repository voxpelli/claude-beads (2 stars, last pushed 26d ago), licensed MIT. It adds 91 tokens to every session and 5,005 once invoked, about $0.0005 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-31.
Other skills, from other repositories
schema-evolve
This skill should be used when the user asks about 'schema drift', 'schema evolution', 'evolve schema', 'schema sync', 'sync schemas', 'update schema fields', 'schema field frequency', 'missing schema fields', 'unused schema fields', 'schema proposal', 'schema cardinality', 'check schema', 'schema audit', 'schema…
knowledge-maintain
This skill should be used when the user asks to fix, repair, or tidy one or more SPECIFIC named notes — 'fix these notes', 'fix the issues in [note]', 'add the missing relations to [note]', 'tidy up [note]', 'fix orphan [note]', 'apply the gardener findings for [note]'. Applies structural fixes (missing sections…
raindrop-triage
This skill should be used when the user asks to 'triage unsorted bookmarks', 'clean up raindrop inbox', 'sort unsorted', 'organize bookmarks', 'raindrop triage', 'process bookmark backlog', 'promote triaged bookmarks', 'classify triaged', 'raindrop cleanup', 'deduplicate bookmarks', 'find duplicate bookmarks', 'tag…
knowledge-garden
This skill should be used when the user asks to audit, health-check, or structurally validate one or more SPECIFIC named notes or a bounded topic cluster — 'audit these notes', 'check this note for orphans or broken links', 'fourth-wall check on [note]', 'validate the structure of [note]', 'spot-check [note]'. Runs a…
nudge
This skill (explicit /nudge only) manages Claude Code feature-adoption nudges sourced from the Basic Memory note main/reference/claude-code-noteworthy-features. Bare /nudge = Mode A (sync): re-read the note, filter out features already marked adopted or declined, and regenerate the tip cache…
session-bookmarks
This skill should be used to save URLs or links found this session as Raindrop bookmarks — triggers: 'bookmark URLs from this session', 'save links we found', 'save notable URLs to Raindrop', 'save session URLs', 'raindrop bookmarks from session'. Scans the current conversation for high-signal URLs discovered during…