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 joris887/exosuit --skill backlog-reviewgit clone --depth 1 https://github.com/joris887/exosuitWrote 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/joris887/exosuit/backlog-review)<a href="https://agentmods.dev/skills/joris887/exosuit/backlog-review"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/backlog-review/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/joris887/exosuit/backlog-review"><img src="https://agentmods.dev/badge/skills/joris887/exosuit/backlog-review.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.00032 | $0.01218 |
| Opus 5 | $0.00016 | $0.00609 |
| Sonnet 5 | $0.00006 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
backlog-review 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 8d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
backlog-review
Execute comprehensive backlog review:
1. Load Current State
Read these files:
- @docs/reference/BACKLOG_INDEX.md (backlog overview)
- docs/reference/backlog/E##-name.md (epic files as needed)
- @docs/reference/PRD_SUMMARY.md (requirements overview, if exists)
- @docs/progress.md (completed work)
2. Theme Coverage Analysis
Map each epic to requirements:
| Epic | Requirements Covered | Coverage % | Gap Analysis |
Priority Validation
- Are high-priority items truly high-value?
- Are dependencies properly ordered?
- Any blocked items that should be deprioritized?
Scope Assessment
- Stories that exceed original scope
- Features creeping in without justification
- Non-goals being violated
3. Story Quality Scan
For each non-done story, validate against the Definition of Ready checklist:
| Criterion | Check |
|---|---|
| Title clear and specific | Describes the change, not the problem |
| Type assigned | One of: feature, bugfix, refactor, spike, infra, testing, docs, security, performance, skill |
| Size classified | TRIVIAL, SMALL, STANDARD, LARGE, or XL. Flag for splitting only when the story spans unrelated topics — file count is not a threshold. See the cohesion test in ideate/references/story-template.md |
| Cohesion test passed | Splitting the story would create artificial seams, not two meaningful pieces |
| 3-7 acceptance criteria | Each testable and specific; LARGE/XL may exceed 3-7, grouped under sub-headings. No "should be fast" or "handle errors properly" |
| Verification commands | Exact commands that prove completion |
| Out of scope defined | At least one explicit exclusion |
| Affected files listed | Proportionate to size, not capped at a fixed number |
| Pattern references | "Follow patterns in [file]" where applicable |
| Dependencies resolved | No unresolved blockers |
| No ambiguous language | No vague terms, all criteria measurable |
| Self-contained | All referenced context included or linked |
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.
- 8d ago First seen · 155 lines · 32 tokens per session scan A d9443a7f0452
backlog-review is a skill published in the GitHub repository joris887/exosuit (4 stars, last pushed 19d ago), licensed MIT. It adds 32 tokens to every session and 1,218 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-08-31.
Other skills, from other repositories
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
project-life
A system for keeping project ideas, tasks, plans, progress, decisions, and lessons in one place. A monorepo-style project workflow is implied, but the input does not define the storage format in full.
lane-contract
A file-based task contract system for describing coding tasks in YAML, including which files a task owns and how it must be checked.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
seo-project-life
A guide to the files, commands, stages, and working process of an SEO project. SEO, or search-engine optimization, is the work of improving a site's visibility in search results.