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 drn/dots --skill retrogit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/retro)<a href="https://agentmods.dev/skills/drn/dots/retro"><img src="https://agentmods.dev/badge/skills/drn/dots/retro.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.00031 | $0.00653 |
| Opus 5 | $0.00015 | $0.00327 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
retro 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective
Structured retrospective for projects, sprints, or incidents. Captures learnings and optionally persists them to the knowledge base.
Arguments
$ARGUMENTS- Optional:--incidentfor post-incident template, or a topic/project name
Context
- Recent commits: !
git log --oneline -20 2>/dev/null | head -20 - Merged PRs: !
gh pr list --state merged --limit 10 2>/dev/null | head -10 - Knowledge base: !
cat context/knowledge/index.md 2>/dev/null | head -30 - Current branch: !
git branch --show-current
Instructions
Step 1: Choose template
IF --incident is in $ARGUMENTS, use the Incident template.
OTHERWISE, use the Standard template.
Step 2: Gather context
Review the recent commits and merged PRs from the context above. Summarize the scope of work that this retro covers. If the user provided a topic, focus on that.
Step 3: Present and collaborate
Standard Template
## Retrospective: <topic or date>
### What Went Well
- <positive outcomes, wins, good patterns>
### What Did Not Go Well
- <pain points, friction, mistakes>
### Action Items
- [ ] <concrete next step with owner if applicable>
### Key Learnings
- <insights to carry forward>
Incident Template
## Post-Incident Review: <incident name>
### Timeline
| Time | Event |
|------|-------|
| | <what happened> |
### Impact
- **Users affected:**
- **Duration:**
- **Severity:**
### Root Cause
<what actually caused the issue>
### What Went Well
- <effective response actions>
### What Did Not Go Well
- <gaps in detection, response, or prevention>
### Action Items
- [ ] <concrete remediation with owner and deadline>
### Follow-ups
- [ ] <longer-term improvements>
Present the template pre-filled with whatever you can infer from the git context. Ask the user to fill in, correct, or expand each section. Iterate until the user is satisfied.
Step 4: Knowledge capture (optional)
IF a knowledge base exists (check context above for context/knowledge/index.md):
- Propose adding key learnings as a new topic or updating an existing topic
- Only add durable, reusable insights — not session-specific details
- Follow the format in
/knowledge(bold entity names, standalone facts, date-stamp volatile info)
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 · 100 lines · 31 tokens per session scan A 79c5d6b45d96
retro is a skill published in the GitHub repository drn/dots (23 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 653 once invoked, about $0.0002 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.