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 review-sprintgit 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/review-sprint)<a href="https://agentmods.dev/skills/atman-33/workhub/review-sprint"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/review-sprint/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/review-sprint"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/review-sprint.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.00043 | $0.00332 |
| Opus 5 | $0.00022 | $0.00166 |
| Sonnet 5 | $0.00009 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
review-sprint 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 6d 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
Review a sprint
Summarize what the sprint actually delivered, anchored on data — not memory.
Steps
- Resolve the sprint (default: latest
sprints/<id>/with ascope.json). - Gather facts:
scope.jsonvs each item's currentstatus→ done / not-done splitrepos/<repo>/pbi-activity.json→ what was actually merged per PBIbacklog/progress-history.jsonl→ points burned over the sprint
- Write
sprints/<id>/review.md(team content language):- Sprint goal: met / partially / missed, with one-line evidence
- Done items (with merge evidence and demo pointers where the PBI notes have them); not-done items with why
- Metrics: committed vs completed points, velocity trend
- Carry-over: agree with the user per unfinished item — back to backlog
(clear
sprint:) or into the next sprint (plan-sprint handles that)
- Update the affected PBI files/backlog table per the carry-over decision, and append an activity-log line.
Rules
- Marking items
doneis the humans' call during the review — record what they decide, don't decide for them.
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.
- 6d ago First seen · 31 lines · 43 tokens per session scan A b6b65a41d857
review-sprint is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 332 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
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
prd
A Product Requirements Document (PRD) writer for large software initiatives. A PRD records the problem, goals, requirements, assumptions, and evidence before implementation begins.
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.
pr
A command for managing pull requests on GitHub or Bitbucket Server. A pull request is a request for other developers to review and merge changes into a project branch.
sync
Rebuild PROJECTSTATE derived fields from artifact files.
shipyard-writing-plans
Use when you have a spec, requirements, or design for a multi-step task — before touching code. Also triggers on "plan this", "break this down", "create tasks", "decompose this feature", or when a task clearly needs more than 2-3 steps to implement. If you're about to start building without a plan, or writing vague…