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/abilityai/abilities/groomnpx skills add Abilityai/abilities --skill groomgit clone --depth 1 https://github.com/Abilityai/abilitiesWhat 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 | $0.00026 | $0.00999 |
| Opus 5 | $0.00013 | $0.00500 |
| Sonnet 5 | $0.00005 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade B, and why
groom scanned grade B 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 2d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls .claude/skills/ How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Groom
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.groom vX.Y — recent: <summary>. Then proceed.
Audit the open issue backlog for this agent. Tags issues with the skill they affect, surfaces missing priorities, and flags stale in-progress work. This is the agent-dev equivalent of backlog grooming — but the "areas" are skills, not features.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| GitHub Issues | Current repo | Yes | Yes | Backlog issues |
| GitHub Labels | skill:, status:, priority:* | Yes | Yes | Apply missing labels |
| Agent Skills | .claude/skills/ | Yes | No | Available skills to tag against |
Process
Step 1: Discover Available Skills
ls .claude/skills/
Build a list of skill names from the directory. These become the valid skill:* label values.
Also check if skill:* labels already exist in the repo:
gh label list --json name --jq '.[].name' | grep '^skill:'
Create any missing skill labels (one per skill directory):
gh label create "skill:$SKILL_NAME" --color "0075CA" --description "Issues affecting the $SKILL_NAME skill" 2>/dev/null || true
Step 2: Fetch All Open Issues
gh issue list --state open --json number,title,body,labels --limit 100
Step 3: Tag Untagged Issues
For each issue that has NO skill:* label:
- Show the issue title and first 3 lines of body
- List available skills
- Ask (in one message, not per-issue): suggest which skill this issue most likely affects based on the title/body, then confirm or let user override
Tagging options per issue:
- A specific skill from
.claude/skills/→ applyskill:<name> - Project-level → no skill tag (affects the agent as a whole, not a specific skill)
- Skip → leave untagged for now
Apply the label:
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.
- 2d ago First seen · 130 lines · 26 tokens per session scan B 9f5d12ac7e59
groom is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 26 tokens to every session and 999 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.