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 agentmods add skills/futuregerald/futuregerald-claude-plugin/ticket-groomingnpx skills add futuregerald/futuregerald-claude-plugin --skill ticket-groominggit clone --depth 1 https://github.com/futuregerald/futuregerald-claude-pluginWrote 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/futuregerald/futuregerald-claude-plugin/ticket-grooming)<a href="https://agentmods.dev/skills/futuregerald/futuregerald-claude-plugin/ticket-grooming"><img src="https://agentmods.dev/badge/skills/futuregerald/futuregerald-claude-plugin/ticket-grooming.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.00084 | $0.02002 |
| Opus 5 | $0.00042 | $0.01001 |
| Sonnet 5 | $0.00017 | $0.00400 |
| Haiku 4.5 | $0.00008 | $0.00200 |
Grade A, and why
ticket-grooming 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/accuracy-rules.md 5.5 KB
- references/adf-posting.md 7.8 KB
- references/configuration.md 925 B
- references/error-handling.md 982 B
- references/estimation-priority.md 1.8 KB
- references/framework-detection.md 12 KB
- references/investigation-prompt.md 3.5 KB
- references/output-templates.md 7.3 KB
- references/pipeline.md 6.2 KB
- references/staff-review-prompt.md 7.3 KB
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 · -3 lines d2cc4dcaf72e
- 5d ago First seen · 159 lines · 84 tokens per session scan A 41b694c4252a
ticket-grooming is a skill published in the GitHub repository futuregerald/futuregerald-claude-plugin (5 stars, last pushed yesterday), with no licence file. It adds 84 tokens to every session and 2,002 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-08-31.
Other skills, from other repositories
linear
Read Linear issues, transition state, and post comments. The entry point for ticket-driven agent workflows.
star-plan-decomposer
Break a research plan down into executable sub-plans with concrete, checkable steps — turning its method or milestones into actionable tasks. Reads the parent plan (written by star-plan-coach and living under metds/plans/), picks a decomposition axis (phase / component / evidence), confirms the unit list, then by…
star-plan-executor
Execute or implement a leaf research sub-plan: turn it into code and run light validation. Orients in the codebase using .env, turns the sub-plan from metds/plans/ into a concrete checked execution plan, implements it with surgical changes, keeps intermediate working files under a plan-specific tasks directory…
star-refs-reviewer
Literature review and related work: per-paper analysis notes plus a verified reference.bib. Builds an auditable base — 5–10 close papers read into notes, plus a classified reference.bib of ≥50 verified entries. No argument finds the method in metds/ and runs the full pass, resuming if metds/refs/ exists; a PLANNAME or…
star-code-release
Open-source or publish the project: gather scattered code, polish it, compile README.md. Consolidates into ${CODENAME}/, sweeping tasks/, wkdrs/ and the root, promoting only code passing a three-part evidence test (the README cites it, an executed leaf needs it, or it reproduces a results.md number), placed by…
star-code-reviewer
Review code quality, docstrings, and whether a plan's code matches what it promised. No argument reviews all of ${CODENAME}/; a PLANNAME (slug / prefix / filename) reviews that plan's files plus conformance (§3 tasks, §4 deliverables, §5 done-criterion); a path reviews that path; diff or a git range reviews changed…