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 skills/loopdive/js2/sprint-retrospectivenpx skills add loopdive/js2 --skill sprint-retrospectivegit clone --depth 1 https://github.com/loopdive/js2What 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 | $0.00026 | $0.00610 |
| Opus 5 | $0.00013 | $0.00305 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
sprint-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 3d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Retrospective
Reviews the sprint and proposes process improvements.
Step 1: Gather data
# Sprint doc
cat plan/issues/sprints/{N}/sprint.md
# Diary entries from this sprint
cat plan/diary.md
# Git history for the sprint
git log --oneline --since="YYYY-MM-DD"
# Recently completed issues
rg -n '^status: done$' plan/issues/*.md | tail -20
# Task completion times (if available)
# Check TaskList or sprint doc task table
Step 2: Identify incidents
For each merge/task, assess:
- Cycle time: how long from claim to merge?
- Friction: rebase failures, conflict resolution, idle waiting?
- Quality: regressions? Tests skipped? Checklist steps missed?
- Communication: too many messages? Wrong recipients? Ignored messages?
Step 3: Categorize
What went well — with evidence:
- Which processes worked as designed?
- Which fixes landed cleanly?
- What saved time vs previous sprints?
What didn't go well — with root cause:
- Each incident: what happened, why, impact
- Systemic patterns across incidents
Step 4: Propose action items
For each problem, propose a specific change to a specific file:
| # | Change | File | Priority |
|---|---|---|---|
| A1 | {what to change} | {which file} | HIGH/MEDIUM/LOW |
Each action item should be:
- Specific: exact file and section to edit
- Testable: how do we know it worked next sprint?
- Small: one rule change, not a process overhaul
Step 5: Write retrospective
Write to plan/issues/sprints/{N}/sprint.md:
# Sprint {N} Retrospective
**Date**: YYYY-MM-DD
**Baseline**: {start numbers}
**Final**: {end numbers}
## What went well
- (with evidence)
## What didn't go well
### Incident 1: {title}
**What happened**: ...
**Root cause**: ...
**Impact**: ...
**Action item**: ...
## Action items summary
| # | Change | File | Priority |
...
## Proposed file edits
(exact diffs for each action item)
Step 6: Review with team
Share the retro with tech lead and user. Don't apply edits unilaterally — propose and wait for approval.
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.
- 3d ago First seen · 97 lines · 26 tokens per session scan A 362d92b98a99
sprint-retrospective is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed 3d ago), licensed Apache-2.0. It adds 26 tokens to every session and 610 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-08-30.
Other skills, from other repositories
migrate-oxfmt
Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
insta-snapshots
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
babel-docs
Babel 7.x/8.x — plugins, presets, config, @babel/core, parser, traverse, types, CLI, preset-env.