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 atman-33/workhub --skill write-retrogit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/write-retro)<a href="https://agentmods.dev/skills/atman-33/workhub/write-retro"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/write-retro/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/atman-33/workhub/write-retro"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/write-retro.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.00046 | $0.00278 |
| Opus 5.5 | $0.00018 | $0.00111 |
| Sonnet 5.5 | $0.00009 | $0.00056 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
write-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 1mo 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.
What it actually says
Write a retrospective
Facilitate a KPT (Keep / Problem / Try) anchored on sprint facts, and keep action items accountable across sprints.
Steps
- Resolve the sprint (default: latest). Read
review.mdif present,progress-history.jsonl, and the previous sprint'sretro.md. - Follow up first: list the previous retro's Try/action items and ask which happened — carry unfinished ones forward explicitly.
- Facilitate KPT: propose seed observations from the data (velocity
swings, items stuck in
doing, scope changes), then collect the team's Keep / Problem / Try. Push each Try to be actionable (owner + when). - Write
sprints/<id>/retro.md(team content language): KPT table, action items with owners, previous-retro follow-up results. - If a Try is a durable process rule, propose promoting it to
knowledge/rules/viateam-kb-save. Append an activity-log line.
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.
- 1mo ago First seen · 24 lines · 46 tokens per session scan A bb7e1c851e19
write-retro is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 278 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-09-03.
Other skills, from other repositories
expo-launchpad-status
Show the current expo-launchpad pipeline state — phase, round, next role, pause reason — read-only.
tasknotes
This skill should be used when the user asks to 'create a task', 'add a TODO', 'plan a sprint', 'organize tasks', 'track time', 'setup Kanban', 'create task from code', 'sync tasks with sprint', 'pomodoro session', 'start pomodoro', 'time estimate', or mentions TaskNotes, task management, or project planning in…
issue-hygiene
How to write an issue somebody can act on, how to triage a pile of them, and the label vocabulary that stays useful. Use when filing, triaging, labelling, closing or linking issues.
aetox-slice
Decomposes a technical specification or plan into vertical tracer-bullet tickets. Calculates directed dependency graphs (DAG), schedules prefactoring first, applies expand-contract sequencing for wide refactors, quizzes the user on ticket granularity, and emits atomic per-ticket files sized for optimal agent context…
project-consolidation
Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. Apps-arena, GitHub-loom), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project…
roadmap-update
Produit un document de roadmap dans output/ en croisant l'état actuel des epics beads avec les décisions et priorités documentées dans le wiki. Applique les règles anti-lissage — ne jamais compléter avec des connaissances d'entraînement, citer le wiki pour chaque affirmation de scope ou de priorité. Triggers — mettre…