Borrowing it
Nothing to install: this file belongs to incubateur-ademe/benefriches. 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/incubateur-ademe/benefriches/main/.claude/skills/to-tickets/SKILL.mdgit clone --depth 1 https://github.com/incubateur-ademe/benefrichesWrote 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/incubateur-ademe/benefriches/to-tickets)<a href="https://agentmods.dev/skills/incubateur-ademe/benefriches/to-tickets"><img src="https://agentmods.dev/badge/skills/incubateur-ademe/benefriches/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/incubateur-ademe/benefriches/to-tickets"><img src="https://agentmods.dev/badge/skills/incubateur-ademe/benefriches/to-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.01020 |
| Opus 5 | $0.00026 | $0.00510 |
| Sonnet 5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Tickets
Break a task's spec into tickets — tracer-bullet vertical slices, each declaring the tickets that block it — published as local files under .agents/tasks/<slug>/issues/. There is no external issue tracker in this project; the files themselves are the tracker.
Process
1. Gather context
Find the task: if a slug is obvious from the conversation, use .agents/tasks/<slug>/DESIGN.md. If ambiguous, list .agents/tasks/*/ and ask. Read the full spec. If no spec exists yet, work from the current conversation directly (and suggest the user run /to-spec first if the discussion is still unsettled).
2. Explore the codebase
If you haven't already, explore the relevant code. Ticket titles and descriptions should use the project's domain vocabulary and respect any ADRs (docs/adr/) in the area touched.
Look for prefactoring opportunities that would make the real change easier — "make the change easy, then make the easy change." A prefactor step, if needed, comes first and blocks everything else.
3. Draft vertical slices
Break the work into tracer-bullet tickets:
- Each ticket cuts a narrow but complete path through every layer it touches (schema → API → UI → tests) — vertical, not a horizontal slice of one layer.
- A completed ticket is demoable or independently verifiable (e.g.
pnpm --filter web testplus a manual check, not "half a feature"). - Each ticket is sized to fit in a single fresh agent context window.
- Any prefactoring is its own ticket, done first.
Give each ticket its blocking edges — the other ticket IDs that must be done 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 — no vertical slice can land green. Don't force it into a tracer bullet; sequence it as expand → migrate → contract:
- Expand: add the new form beside the old so nothing breaks.
- Migrate: move call sites over in batches sized by blast radius (per app, per directory), each batch its own ticket blocked by the expand ticket, keeping
pnpm -r typecheck && pnpm -r lint && pnpm -r format && pnpm -r testgreen batch to batch. - Contract: delete the old form once no caller remains, blocked by every migrate batch.
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 Changed d4b35c86430c
- 12d ago First seen · 85 lines · 52 tokens per session scan A 3551957ffa2a
to-tickets is a skill published in the GitHub repository incubateur-ademe/benefriches (45 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 1,020 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.