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/TheLobbi/claudeWrote 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/commands/thelobbi/claude/backlog-groom)<a href="https://agentmods.dev/commands/thelobbi/claude/backlog-groom"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/backlog-groom.svg" alt="Measured on agentmods" 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.00000 | $0.02180 |
| Opus 5 | $0.00000 | $0.01090 |
| Sonnet 5 | $0.00000 | $0.00436 |
| Haiku 4.5 | $0.00000 | $0.00218 |
Grade A, and why
backlog-groom scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "$JIRA_URL/rest/api/3/search" \ How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Grooming Command
Facilitate backlog refinement and story preparation.
Instructions
1. Setup
```bash export JIRA_URL="${JIRA_URL:-https://your-domain.atlassian.net}" export JIRA_AUTH=$(echo -n "$JIRA_EMAIL:$JIRA_API_TOKEN" | base64) ```
2. Identify Stories Needing Refinement
```bash echo "=== Stories Needing Refinement ==="
Missing estimates
echo ""
echo "📊 Missing Story Points:"
curl -s -X POST "$JIRA_URL/rest/api/3/search"
-H "Authorization: Basic $JIRA_AUTH"
-H "Content-Type: application/json"
-d '{
"jql": "project = GA AND type = Story AND status = Backlog AND "Story Points" is EMPTY ORDER BY rank",
"fields": ["summary", "priority"],
"maxResults": 20
}' | jq '.issues[] | "(.key): (.fields.summary)"'
Missing acceptance criteria
echo ""
echo "📝 Missing/Short Description:"
curl -s -X POST "$JIRA_URL/rest/api/3/search"
-H "Authorization: Basic $JIRA_AUTH"
-H "Content-Type: application/json"
-d '{
"jql": "project = GA AND type = Story AND status = Backlog AND (description is EMPTY OR description !~ "acceptance criteria")",
"fields": ["summary"],
"maxResults": 20
}' | jq '.issues[] | "(.key): (.fields.summary)"'
Large stories (>8 points)
echo ""
echo "🔨 Large Stories (consider splitting):"
curl -s -X POST "$JIRA_URL/rest/api/3/search"
-H "Authorization: Basic $JIRA_AUTH"
-H "Content-Type: application/json"
-d '{
"jql": "project = GA AND type = Story AND "Story Points" > 8 AND status = Backlog",
"fields": ["summary", "customfield_10016"],
"maxResults": 10
}' | jq '.issues[] | "(.key): (.fields.summary) ((.fields.customfield_10016) pts)"'
```
3. Review Top Backlog Items
```bash
echo ""
echo "=== Top 15 Backlog Items ==="
curl -s -X POST "$JIRA_URL/rest/api/3/search"
-H "Authorization: Basic $JIRA_AUTH"
-H "Content-Type: application/json"
-d '{
"jql": "project = GA AND type in (Story, Bug) AND status = Backlog ORDER BY rank",
"fields": ["summary", "priority", "customfield_10016", "labels"],
"maxResults": 15
}' | jq '.issues[] | {
key,
summary: .fields.summary,
priority: .fields.priority.name,
points: .fields.customfield_10016,
labels: .fields.labels
}'
```
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 First seen · 267 lines · 0 tokens per session scan A d9964d7d901a
backlog-groom is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,180 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.