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/dojogenesis/mcp/retrospectivenpx skills add DojoGenesis/mcp --skill retrospectivegit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/retrospective)<a href="https://agentmods.dev/skills/dojogenesis/mcp/retrospective"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/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 | $0.00056 | $0.02091 |
| Opus 5 | $0.00028 | $0.01045 |
| Sonnet 5 | $0.00011 | $0.00418 |
| Haiku 4.5 | $0.00006 | $0.00209 |
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 5d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective Skill
Version: 1.1 Author: Tres Pies Design Purpose: Structured, repeatable process for conducting sprint retrospectives, harvesting learnings, and feeding them back into collaborative practice.
I. Philosophy: Harvest, Not Post-Mortem
A retrospective is not a post-mortem. It is not about blame or judgment. It is a harvest. After a season of hard work, we pause to gather the fruits of our labor — not just the features we shipped, but the wisdom we gained in the process. It is a practice of gratitude, honesty, and a commitment to continuous learning.
This skill turns the informal act of looking back into a formal ritual, ensuring that valuable lessons from each sprint are not lost but integrated into shared memory and future workflows.
II. When to Use This Skill
- After a major release (e.g., after shipping v1.0)
- After a significant milestone (e.g., completing a major refactor)
- When a project feels stuck or has encountered significant friction
- At regular intervals (e.g., monthly) to maintain a cadence of reflection
III. The 5-Step Retrospective Workflow
Step 1: Initiate the Retrospective
State the intention to conduct a retrospective. Frame it as a positive and necessary part of the workflow. Accept: sprint number, version, date range, or informal period ("the last two weeks").
Step 2: Gather Context
Pull relevant data from connected tools to ground the retrospective in evidence:
- ~~project tracker: Completed tickets, velocity, burndown
- ~~chat: Notable discussions, decisions, blockers raised
- ~~repository: Merged PRs, deployment history, code changes
If no integrations are connected, ask the user to share context verbally.
Step 3: Facilitate the Three Core Questions
Ask these one at a time, conversationally — never dump all three at once:
- What went well? — Celebrate successes, name specific wins, acknowledge contributors. What should we amplify?
- What was hard? — Identify pain points without blame. Focus on systemic issues, not individual failures. What were the sources of friction?
- What would we do differently? — Concrete changes, not vague intentions. Each "differently" should be actionable.
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.
- 5d ago First seen · 237 lines · 56 tokens per session scan A af4d15a96ddc
retrospective is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 2,091 once invoked, about $0.0003 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
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
prune-npm-overrides
Audit the pnpm overrides a repo already carries, remove the ones upstream has since fixed, and require a justification comment on every one that stays. The counterpart to fix-npm-vulnerability. Use when asked to check, clean up, or prune the overrides, or when an override's tracking issue comes up for review.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
file-crdb-issue
Use when filing, creating, or reporting GitHub issues for CockroachDB. Use when asked to open a bug report, feature request, investigation issue, or performance inquiry. Also use when the user mentions wanting to track a problem, report a regression, or document unexpected behavior in CockroachDB.