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 tsai09495/matt-pocock-engineering --skill to-ticketsgit clone --depth 1 https://github.com/tsai09495/matt-pocock-engineeringWrote 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/tsai09495/matt-pocock-engineering/to-tickets)<a href="https://agentmods.dev/skills/tsai09495/matt-pocock-engineering/to-tickets"><img src="https://agentmods.dev/badge/skills/tsai09495/matt-pocock-engineering/to-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/tsai09495/matt-pocock-engineering/to-tickets"><img src="https://agentmods.dev/badge/skills/tsai09495/matt-pocock-engineering/to-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.00043 | $0.00930 |
| Opus 5 | $0.00022 | $0.00465 |
| Sonnet 5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
to-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 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Tickets
Turn an established plan into thin, independently understandable implementation tickets. Selecting this skill does not authorize tracker or repository writes.
Read the configured issue-tracker convention in docs/agents/issue-tracker.md when present.
Process
1. Gather source context
Read the complete referenced spec, issue, plan, comments, repository guidance, glossary, and relevant ADRs. Explore enough code to understand existing seams and integration paths. Do not reopen already-settled product decisions.
2. Draft tracer-bullet slices
Each normal ticket must:
- deliver a narrow but complete path through every affected layer;
- be independently demoable or verifiable;
- fit in one fresh implementation context;
- state acceptance criteria in observable terms;
- use project domain language;
- avoid speculative cleanup and horizontal “all schema,” “all API,” or “all UI” phases.
Write each acceptance criterion as one concrete observable trace. Keep mutually exclusive success, exhaustion, decline, cancellation, and other terminal paths in separate criteria; never compress them into wording that implies work continues after a terminal outcome.
Do not split tests, metrics, documentation, or other supporting work into a standalone ticket merely to create parallelism. Keep support work with the behavior it proves or observes unless it delivers an independently usable and verifiable outcome before any downstream behavior exists. A ticket with Blocked by: None is not independent when its own acceptance criteria require behavior introduced by another ticket; model that edge explicitly or redraw the slice.
Prefactoring that makes the change safe may be its own ticket when it has independent verification and genuinely blocks later behavior.
3. Model blocking edges and frontier
For every ticket, list only the tickets that must finish before it can start. Tickets with no unresolved blockers form the frontier and can be selected independently. Do not convert mere preference into a dependency.
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.
- 12d ago First seen · 99 lines · 43 tokens per session scan A ba0f75adacb2
to-tickets is a skill published in the GitHub repository tsai09495/matt-pocock-engineering (2 stars, last pushed 18d ago), licensed MIT. It adds 43 tokens to every session and 930 once invoked, about $0.0002 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
manage-taskboard
Manage Codex Taskboard / e-taskboard work with taskctl. Use for taskboard issue IDs, status sync, comments, or taskctl cloud setup—not for unrelated product docs.
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.