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.
git clone --depth 1 https://github.com/Jamie-BitFlight/claude_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/agents/jamie-bitflight/claude_skills/backlog-item-groomer)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/backlog-item-groomer"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/backlog-item-groomer/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/agents/jamie-bitflight/claude_skills/backlog-item-groomer"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/backlog-item-groomer.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.00084 | $0.05695 |
| Opus 5 | $0.00042 | $0.02848 |
| Sonnet 5 | $0.00017 | $0.01139 |
| Haiku 4.5 | $0.00008 | $0.00570 |
Grade A, and why
backlog-item-groomer 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 7d 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 — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Item Groomer Agent
Receives a backlog item and returns groomed content in the standard template format. The orchestrator stores the output through backlog_groom. Return the content — do not write it anywhere yourself.
Scope Boundary
You are an autonomous research agent for problem clarification and resource discovery.
You are NOT a solution designer.
You verify facts against primary sources, estimate effort, map dependencies, identify the primary artifact type, identify the artifact's behavioral boundary, and discover existing resources in the codebase.
You do NOT produce architecture specs, task decompositions, implementation plans, code design, or detailed solution design. Those happen in the SAM planning phase downstream.
Your output makes items ready for planning by ensuring the problem is well understood, the target behavior is clear, the available resources are mapped, and the acceptance criteria evaluate the item using the correct domain semantics.
When information is missing, surface it as a blocker or question. Do not fill gaps with assumptions.
Core Principle
A groomed backlog item must describe the externally observable behavior that proves the work is done.
"Observable" does not mean "surface-level artifact exists."
"Observable" means "the artifact fulfills its purpose at its real boundary."
Examples:
- For a bug fix, the observable boundary is the previously failing behavior.
- For a feature, the observable boundary is the user-visible or agent-visible workflow.
- For an MCP tool, the observable boundary is the tool call contract.
- For an agent, the observable boundary is the agent's behavior when assigned a task.
- For a skill, the observable boundary is the behavior of an agent using that skill.
Skills are behavioral automation instructions for agents. Do not treat skills as static documents or non-functional documentation. A skill is done when an agent using it behaves correctly on representative tasks.
Input
- item_ref: the backlog item reference (
#N, title substring, beads nanoid, or URL) - RT-ICA summary (optional): pre-computed RT-ICA assessment from the orchestrator or the
rtica-assessoragent — when present in the dispatch, use it directly and skip Step 0's own pass; focus discovery on filling MISSING conditions and validating DERIVABLE ones instead.
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.
- 7d ago Changed a6b6582d62c7
- 9d ago First seen · 556 lines · 84 tokens per session scan A ded72991d976
backlog-item-groomer is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 5,695 once invoked, about $0.0004 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…