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 Magnus-Gille/claude-skills --skill ticket-fleetgit clone --depth 1 https://github.com/Magnus-Gille/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/skills/magnus-gille/claude-skills/ticket-fleet)<a href="https://agentmods.dev/skills/magnus-gille/claude-skills/ticket-fleet"><img src="https://agentmods.dev/badge/skills/magnus-gille/claude-skills/ticket-fleet/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/magnus-gille/claude-skills/ticket-fleet"><img src="https://agentmods.dev/badge/skills/magnus-gille/claude-skills/ticket-fleet.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.00055 | $0.00349 |
| Opus 5.5 | $0.00022 | $0.00140 |
| Sonnet 5.5 | $0.00011 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
ticket-fleet 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 yesterday.
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.
What it actually says
Ticket-fleet compatibility
A "ticket" here is a Plane ticket, identified by its key (for example GRIM-87),
not a GitHub issue. A PR for it stays on GitHub and references the key plus the
Plane URL (Refs GRIM-87).
For an existing /ticket-fleet request, use the single delivery workflow in
../ship-it/SKILL.md at the PR endpoint. It ends
after publication and fresh checks; it never merges. If the user separately
requests a later endpoint, handle that as an explicit /ship-it request under
its normal workflow. For multi-ticket coordination, read ship-it's
batch reference.
An explicit /ticket-fleet invocation that names the task and owning
repository is the user's request to prepare and publish PRs as needed to reach
this endpoint, subject to global policy and exact target/change preview. If the
repository or target is unclear, clarify it before publication. Automatic
skill selection does not authorize publication.
This compatibility entrypoint does not launch headless sessions, grant tool
permissions, invoke local models, or authorize merge or deployment. The global
AGENTS.md remains the authority source for mutation boundaries. Legacy runner
scripts now fail closed and direct callers to /ship-it.
What ships with it
7 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.
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.
- yesterday Changed · +4 lines · +12 tokens per session 77a3bac79660
- 20d ago Changed · -84 lines · -30 tokens per session 5a9568f0c50c
- 2mo ago First seen · 109 lines · 73 tokens per session scan A 00277d8c9235
ticket-fleet is a skill published in the GitHub repository Magnus-Gille/claude-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 349 once invoked, about $0.0002 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
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)…