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 agentmods add skills/assisjp/specflow/to-ticketsnpx skills add assisjp/specflow --skill to-ticketsgit clone --depth 1 https://github.com/assisjp/specflowWrote 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/assisjp/specflow/to-tickets)<a href="https://agentmods.dev/skills/assisjp/specflow/to-tickets"><img src="https://agentmods.dev/badge/skills/assisjp/specflow/to-tickets.svg" alt="Measured on agentmods" 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 | $0.00088 | $0.01588 |
| Opus 5 | $0.00044 | $0.00794 |
| Sonnet 5 | $0.00018 | $0.00318 |
| Haiku 4.5 | $0.00009 | $0.00159 |
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 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Tickets
Break the work into tickets — tracer-bullet vertical slices, each declaring the tickets that block it. The dependency graph is explicit and declared, never inferred from titles.
Process
Mode: healing a returned ticket
Check the input before anything else. If it is a single ticket carrying a returned marker — a returned label on the issue, or a Returned: line in the local ticket file — you are in healing mode, not slicing mode. Skip steps 1–4 entirely. Rewrite only that one ticket, republish it to the same issue/file, and clear its marker as the "Clearing a returned marker" paragraph in step 5 directs. Do not touch any neighbouring ticket and do not re-derive the graph — the blocking edges of the other tickets are not yours to move. Otherwise — a whole spec, plan, or settled conversation to slice — run steps 1–5 as written.
1. Gather context
Work from what is in the conversation. If the user passes a reference (a spec path, an issue number or URL), fetch it and read the full body and comments.
2. Explore the codebase (optional)
If you have not already, explore to understand the current state. Ticket titles and descriptions use the project's CONTEXT.md glossary vocabulary, and respect ADRs in the area you touch. Look for prefactoring that makes 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 fits in a single fresh context window.
- Any prefactoring goes first.
Give each ticket its blocking edges — the tickets that must complete before it can start. A ticket with no blockers can start immediately.
Wide refactors are the exception. 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 and no vertical slice can land green. Sequence it as expand → migrate → contract: first add the new form beside the old so nothing breaks; then migrate call sites in batches sized by blast radius (per package, per directory), each batch a ticket blocked by the expand, CI green batch to batch because the old form still exists; finally delete the old form in a ticket blocked by every migrate batch. If even the batches cannot stay green alone, 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.
- 5d ago First seen · 80 lines · 88 tokens per session scan A abab0e64b7e7
to-tickets is a skill published in the GitHub repository assisjp/specflow (17 stars, last pushed 25d ago), licensed MIT. It adds 88 tokens to every session and 1,588 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…