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 skills add phobologic/claude_code_helpers --skill implement-ticketgit clone --depth 1 https://github.com/phobologic/claude_code_helpersWrote 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/phobologic/claude_code_helpers/implement-ticket)<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/implement-ticket"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/implement-ticket/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/skills/phobologic/claude_code_helpers/implement-ticket"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/implement-ticket.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.00028 | $0.02047 |
| Opus 5.5 | $0.00011 | $0.00819 |
| Sonnet 5.5 | $0.00006 | $0.00409 |
| Haiku 4.5 | $0.00003 | $0.00205 |
Grade A, and why
implement-ticket 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 12d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Ticket
Phase 0 — Argument parsing
Parse $ARGUMENTS:
- Ticket IDs are space-separated tokens before any
-- - Everything after
--is extra instructions that inform the design phase - Examples:
/implement-ticket 42— single ticket/implement-ticket 42 43— process both, sequentially/implement-ticket 42 -- focus on error handling, skip migration— ticket with constraints
Phase 1 — Ticket selection
If ticket IDs were provided: run tk show-multi <ids> to load full context.
If any loaded ticket has type == "epic":
- Run
tk query '.parent == "<epic-id>"'to find its child tickets - Filter to only eligible children (status is not
closedorin-progress) - If no eligible children remain, inform the user the epic is fully complete or all work is in-progress, and stop
- Present suggested next tickets with reasoning (same UX as the no-args path: 2–3 picks + full list)
- Ask the user which child ticket(s) to proceed with
- Continue the rest of the skill with those child IDs — never implement the epic itself
If no IDs provided:
- Run
tk readyto get unblocked work - Read each ticket's description to understand scope and context
- Present two things to the user:
- Suggested next tickets (2–3 picks with reasoning — e.g., "unblocks the most downstream work", "highest priority", "quickest win based on scope")
- Full ready list for their reference
- Ask the user which ticket(s) to proceed with
Phase 2 — Complexity triage
Read the selected ticket(s) and parent epic (if set). Make a judgment call:
Straightforward — typo, config change, single clear action with no design ambiguity:
- Describe what you'll do in 1–2 sentences
- Ask the user for a quick go-ahead
- Skip Phases 3–4 and proceed directly to implementation
Complex — new feature, tricky bug, or non-obvious design decisions:
- Proceed through the full design and planning flow below
Phase 3 — Requirements clarification + acceptance criteria
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.
- 12d ago Changed 4c4e1450b7f8
- 1mo ago First seen · 188 lines · 28 tokens per session scan A b1e63b5e1ac8
implement-ticket is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 2,047 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…