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 flurdy/agent-skills --skill backlog-groomgit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/backlog-groom)<a href="https://agentmods.dev/skills/flurdy/agent-skills/backlog-groom"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/backlog-groom.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00060 | $0.04727 |
| Opus 5 | $0.00030 | $0.02364 |
| Sonnet 5 | $0.00012 | $0.00945 |
| Haiku 4.5 | $0.00006 | $0.00473 |
Grade A, and why
backlog-groom 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 today.
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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Groom — Per-Bead Quality Audit
Walk the open backlog and ask, for each bead: is this any good? Flag hygiene, priority, lifecycle, structure, and duplicate problems, propose a concrete fix for each, and only mutate on explicit approval.
This is the hygiene counterpart to the intake/reconciliation skills — it is the only one that systematically reads every open bead and improves its quality.
Relationship to other tools
/triageis forward intake: prompt/Jira → new bead(s), with dup-check and splitting at creation time. The groomer does not create beads from prompts and does not re-implement splitting — when a bead obviously needs splitting, it hands the bead to/triage./triage <bead-id>(refine mode) is the depth counterpart to this sweep: it investigates one existing bead against the code, then deepens, corrects, or splits it. Hand a bead there whenever grooming it needs real investigation rather than a one-shot edit — see the "be fast" rule below.
/tracking-sweepis cross-system drift (Jira ↔ beads ↔ PRs), read-only. The groomer does not re-implement cross-system linking — when a bead lacks a Jira/Trello link, it flags it and points at/tracking-sweep(or/trello-beads).tracking-auditor(agent) is per-branch: does THIS diff match its ticket? Unrelated./backlog-groom(this skill) is per-bead quality of the backlog itself: descriptions, labels, priority, lifecycle, structure, duplicates.
If a finding belongs to one of those tools, delegate — don't duplicate its logic.
Usage
/backlog-groom # Read-only sweep of open beads → proposal report. Changes nothing.
/backlog-groom apply # After showing the report, batch-apply the SAFE proposals on approval;
# destructive ones still confirm one at a time.
/backlog-groom all # Widen scope to open + ready + blocked (default is open only).
/backlog-groom labels # Just the DB-wide label-normalisation pass (fast).
/backlog-groom lint # Opt in to template-conformance checks (AC / Steps / Success Criteria).
/backlog-groom <bead-id> … # Groom only the named beads.
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.
- today Changed · -81 tokens per session e629d08649df
- 8d ago First seen · 232 lines · 141 tokens per session scan A dd64224e2032
backlog-groom is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 4,727 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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.