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/vinnie357/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/commands/vinnie357/claude-skills/groom-epics)<a href="https://agentmods.dev/commands/vinnie357/claude-skills/groom-epics"><img src="https://agentmods.dev/badge/commands/vinnie357/claude-skills/groom-epics/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/commands/vinnie357/claude-skills/groom-epics"><img src="https://agentmods.dev/badge/commands/vinnie357/claude-skills/groom-epics.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.00012 | $0.01675 |
| Opus 5 | $0.00006 | $0.00838 |
| Sonnet 5 | $0.00002 | $0.00335 |
| Haiku 4.5 | $0.00001 | $0.00168 |
Grade A, and why
groom-epics 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 9d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix VantageEx compatibility issues across one epic or a whole project. Scoped, pre-flight-gated, and offloads the audit pass to a haiku mapper so the parent session never holds full descriptions for an entire project.
Steps
- Load the
/linearskill - Read the epic format spec at
references/epic-format.md - Read the audit checklist at
references/audit-checklist.md - Read the team definition template at
templates/0.1.0/team-definition.md
Phase A — Pre-flight
Run on every invocation. Halt with a clear message if any check fails — never partial-progress.
-
Verify Linear access. Pass if either:
- The Linear MCP server is registered (
claude mcp listshows alinear-serverentry), OR LINEAR_API_KEYenvironment variable is set.
If neither, halt with:
Linear access is not configured. Set up one of:
claude mcp add --transport http linear-server https://mcp.linear.app/mcpthen/mcpto authenticateexport LINEAR_API_KEY=<key>(see https://linear.app/settings/account/security)
- The Linear MCP server is registered (
-
Resolve scope from arguments:
--issue=<key>(e.g.,--issue=VIN-42) → single-issue path. Skip Phase B; audit + groom inline.--project=<slug>→ project path. Continue to Phase B.- Neither → ask the user which scope.
-
For project scope: identify open-state IDs. Query the team's
workflowStatesand keep only states whosetypeis in{triage, backlog, unstarted, started}. Exclude any state whosetypeiscompletedorcanceled— grooming closed epics is forbidden and would mutate finished work. -
Count candidates. Query the project for issues in the open-state IDs only. Print the count.
-
Overload gate. If
count >= --max-issues(default50), refuse to proceed without--confirm-bulk. Suggest narrowing with--issue=<key>or batching as a follow-up. This is a hard gate —--autodoes not bypass it.
Phase B — Mapper (project scope only)
Spawn a single read-only haiku agent to audit all candidates and return a compact digest. The parent session never holds the full descriptions.
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.
- 9d ago First seen · 163 lines · 12 tokens per session scan A 20a6dd771792
groom-epics is a command published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 1,675 once invoked, about $0.0001 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 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.