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 mrclrchtr/supi --skill gather-retrospectivesgit clone --depth 1 https://github.com/mrclrchtr/supiWrote 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/mrclrchtr/supi/gather-retrospectives)<a href="https://agentmods.dev/skills/mrclrchtr/supi/gather-retrospectives"><img src="https://agentmods.dev/badge/skills/mrclrchtr/supi/gather-retrospectives/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/mrclrchtr/supi/gather-retrospectives"><img src="https://agentmods.dev/badge/skills/mrclrchtr/supi/gather-retrospectives.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.00038 | $0.01215 |
| Opus 5.5 | $0.00015 | $0.00486 |
| Sonnet 5.5 | $0.00008 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
gather-retrospectives 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 2d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gather retrospectives
Collect once
Default to the current workspace tree and all dates. Other projects and sibling worktrees require user-approved scope. A topic (“about supi-agent”) is not a producer filter: keep both sources unless asked for delegated runs (--source supi-agent) or Reviewer Runs (--source supi-review).
Resolve the script relative to this skill directory and run directly:
output_dir=$(mktemp -d)
node "<absolute-skill-directory>/scripts/collect.mjs" \
--workspace "$PWD" --output "$output_dir/evidence.json"
The command is ready to execute. See CLI flags for scope, date, storage, scan-limit, and display options. If execution is unavailable, report that limitation.
Read to completion
The temporary evidenceFile freezes all matching reports and scan coverage. Stdout supplies assessment text and citations within 16 KB. Use the displayed text directly, then execute nextCommand until display.complete is true. These follow-ups read the snapshot, not session storage, so new sessions cannot shift the results. Oversized assessments continue under the same ref with contiguous UTF-16 textRange offsets; interpret their fragments together.
coverage.completedescribes the scan independently of display completion. Disclose scan limits, malformed entries, skipped symlinks, or read failures when false.summarycounts the entire deduplicated snapshot: reports by producer/status, containing sessions, and earliest/latest report dates. Reports from one session remain correlated.- If a user requests a bounded sample, stop at that bound and disclose unread reports rather than claiming exhaustive coverage.
- No matching reports: report the empty result and coverage limitations in at most 100 words, link the evidence, and finish. Optional capture and successful-task selection mean absence of feedback is not absence of regressions.
For a later targeted reread, select references without rescanning:
node "<absolute-skill-directory>/scripts/collect.mjs" \
--read "/absolute/evidence.json" --refs "R-<id>,R-<id>"
What ships with it
11 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.
- evals/evals.json 4.6 KB
- evals/files/incomplete-sessions/broken.jsonl 163 B
- evals/files/incomplete-sessions/old.jsonl 464 B
- evals/files/overflow-sessions/a.jsonl 40 KB
- evals/files/overflow-sessions/b.jsonl 11 KB
- evals/files/overflow-sessions/z-clone.jsonl 28 KB
- evals/files/sessions/clone.jsonl 628 B
- evals/files/sessions/main.jsonl 2.4 KB
- evals/files/sessions/other.jsonl 489 B
- scripts/collect.mjs 14 KB runs code
- scripts/snapshot.mjs 6.7 KB runs code
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.
- 2d ago First seen · 73 lines · 38 tokens per session scan A 6a2199e538d7
gather-retrospectives is a skill published in the GitHub repository mrclrchtr/supi (103 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,215 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-10-27.
Other skills, from other repositories
muse-delegate
Delegate a coding task to Muse Code (muse) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Muse — phrasings like "have Muse do X", "delegate this to Muse", "run it through Muse", or "use Muse to implement/fix/refactor" — or wants…
pi-parity-review
Adversarially verify that a ported change is faithful to the original pi implementation (TS source + published npm build). Use after porting upstream pi changes, or standalone on any area of this repo ("is X faithful to pi?").
pi-go-review
Review ported Go code for idiomatic quality — that the port maximizes Go rather than transliterating TypeScript. Use after porting upstream pi changes, or standalone on any diff in this repo.
gh-address-comments
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
review
Review a change for correctness, security, and missing tests.
review-pr
Deeply review a GitHub pull request.