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 run-ticketsgit 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/run-tickets)<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/run-tickets"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/run-tickets/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/run-tickets"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/run-tickets.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.00085 | $0.04664 |
| Opus 5.5 | $0.00034 | $0.01866 |
| Sonnet 5.5 | $0.00017 | $0.00933 |
| Haiku 4.5 | $0.00009 | $0.00466 |
Grade A, and why
run-tickets 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 5d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tickets
You prepare a ticket run, hand it to the run-tickets-engine workflow, and report the
result. The workflow script owns all scheduling: dependency order, the worktree
pool, verification, rework caps, and merge serialization. You do not implement,
review, or route messages. Everything you do happens before the workflow starts
or after it returns.
Progress:
- [ ] Phase 0: parse arguments
- [ ] Phase 1: plan, put decisions to the owner, confirm
- [ ] Phase 2: set up (run-tickets-setup, gate baseline)
- [ ] Phase 3: write the run record, launch the workflow
- [ ] Phase 4: when it completes, read finish.md and follow it
Phase 0: Parse arguments
$ARGUMENTS is either a single epic ID (its open children are the run) or one
or more ticket IDs. --resume means a previous run halted or was interrupted:
include tickets already marked in_progress and reuse existing branches (see
"If the run halts or dies" in Phase 3). --slots N overrides the pool size.
Strip both flags before calling run-tickets-plan, except that --resume
becomes --include-in-progress.
The user's request wins over this skill's defaults. If they name an integration branch, a slot count, gates, or anything else this skill would otherwise choose, use theirs and say so in the plan.
No arguments: print the usage line from argument-hint and stop.
Phase 1: Plan
run-tickets-plan [--include-in-progress] <args>
It prints JSON: tickets (topologically ordered, each with in-set deps,
tags, has_ac, files, reviewed), excluded (with reasons), decisions,
decision_candidates, cycles, overlaps, unannotated, large,
setup_warnings, integration, and stats. If tickets is empty, show
excluded and stop.
Human gates. Tickets tagged needs-human are excluded, with everything
downstream of them. If a ticket's text says a person must do or approve it
(for example "NO AGENT MAY CLOSE THIS TICKET") but it lacks the tag, point it
out and offer tk set <id> --tags <existing>,needs-human, then re-run the
planner, rather than excluding it by hand.
What ships with it
1 file 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.
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.
- 5d ago Changed · +24 lines · +9 tokens per session 3ecf432231a9
- 12d ago First seen · 328 lines · 76 tokens per session scan A 33683737bdaa
run-tickets is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 4,664 once invoked, about $0.0003 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-10-05.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…
implement-issue
Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.