Borrowing it
Nothing to install: this file belongs to mcwalrus/oppertunity-party. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mcwalrus/oppertunity-party/main/.agents/skills/to-tickets/SKILL.mdgit clone --depth 1 https://github.com/mcwalrus/oppertunity-partyWrote 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/mcwalrus/oppertunity-party/to-tickets)<a href="https://agentmods.dev/skills/mcwalrus/oppertunity-party/to-tickets"><img src="https://agentmods.dev/badge/skills/mcwalrus/oppertunity-party/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/mcwalrus/oppertunity-party/to-tickets"><img src="https://agentmods.dev/badge/skills/mcwalrus/oppertunity-party/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.00054 | $0.01237 |
| Opus 5 | $0.00027 | $0.00619 |
| Sonnet 5 | $0.00011 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00124 |
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 8d 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.
This is a copy
94% identical to to-tickets — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Tickets
Break a plan, spec, or conversation into a set of tickets — tracer-bullet vertical slices, each declaring the tickets that block it.
The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.
2. Explore the codebase (optional)
If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."
3. Draft vertical slices
Break the work into tracer bullet tickets.
- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer
- A completed slice is demoable or verifiable on its own
- Each slice is sized to fit in a single fresh context window
- Any prefactoring should be done first
Give each ticket its blocking edges — the other tickets that must complete before it can start. A ticket with no blockers can start immediately.
Wide refactors are the exception to vertical slicing. A wide refactor is one mechanical change — rename a column, retype a shared symbol — whose blast radius fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as expand–contract. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket — green is promised only there.
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.
- 8d ago First seen · 106 lines · 54 tokens per session scan A 5ecdf1d4df8a
to-tickets is a skill published in the GitHub repository mcwalrus/oppertunity-party (0 stars, last pushed 16d ago), licensed MIT. It adds 54 tokens to every session and 1,237 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to to-tickets, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
timeline-operator
Use this skill to review the event and snapshot history of a tracked FYI request, identify stale requests, and prepare concise operator notes.
next-action-operator
Purpose: choose the next best operator action for a tracked FYI request using local state, snapshot analysis, and follow-up packs.
update-status
Use when the user reports progress on a role and wants the board updated. Triggers: /update-status, "move X to tech interview", "I got an HR screen with Y", "Z rejected me", "got an offer from W", "schedule my interview with V". Moves a vacancy through the pipeline, appends a timestamped statusDetail (preserving…
launch-readiness
Interrogates a planned launch — what is unowned, the rollback plan, the comms and enablement gaps, what breaks if adoption is 10x or 0.1x of expectation, and the explicit kill criteria. Produces the gap list specific to this launch; never a generic checklist.
neural-tasks
Manage the full task lifecycle in the neural knowledge graph — list, create, update status and priority. Tasks connect to code nodes and appear in every prompt via the context hook.
neural-add-task
Manually log a task or phase into the neural memory knowledge graph. Links the task to related code files so it appears in semantic search results.