Borrowing it
Nothing to install: this file belongs to the-sid-dani/second-brain-os. 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/the-sid-dani/second-brain-os/main/.agents/skills/to-tickets/SKILL.mdgit clone --depth 1 https://github.com/the-sid-dani/second-brain-osWrote 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/the-sid-dani/second-brain-os/to-tickets)<a href="https://agentmods.dev/skills/the-sid-dani/second-brain-os/to-tickets"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/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/the-sid-dani/second-brain-os/to-tickets"><img src="https://agentmods.dev/badge/skills/the-sid-dani/second-brain-os/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.00080 | $0.01642 |
| Opus 5.5 | $0.00032 | $0.00657 |
| Sonnet 5.5 | $0.00016 | $0.00328 |
| Haiku 4.5 | $0.00008 | $0.00164 |
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 7d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Tickets
Break a spec, plan, or conversation into a set of tickets. Each ticket is a tracer-bullet vertical slice that declares the tickets that block it. The work can be code or knowledge work.
Resolve the project, its tracker and its paths from docs/agents/project-context.md. If a skill earlier in this conversation already resolved them, reuse that.
Process
1. Gather context
Work from whatever is already in the conversation. If the user passes a reference as an argument, read its full body. The reference can be a spec path or a ticket file.
2. Explore (optional)
If you haven't already, look at the current state of the work.
- Code: explore the codebase.
- Knowledge work: read the project folder and any earlier version of the artifact.
Ticket titles and descriptions use the project's own vocabulary (CONTEXT.md or glossary.md) and respect its recorded decisions.
Look for prep work that makes everything after it easier. "Make the change easy, then make the easy change."
- Code: prefactoring.
- Knowledge work: gathering the data, getting access, building the doc skeleton, pulling last year's version.
3. Draft vertical slices
Break the work into tracer bullet tickets.
- Each slice cuts a narrow but COMPLETE path through every layer. It's vertical, NOT a horizontal slice of one layer.
- Code: schema, API, UI, tests.
- Knowledge work: one section fully drafted, sourced and reviewed, never "write all the intros" then "add all the numbers".
- A completed slice is demoable or verifiable on its own. Someone can check or sign off on it alone.
- Each slice is sized to fit in a single fresh context window.
- Any prep work comes first, as its own ticket.
Single artifacts with stages are the knowledge-work exception. One video or one deck has stages that are horizontal by nature: research, script, record, edit, package. Stage tickets are fine, but each stage must end in something a person can review on its own: the brief approved, the script and title shortlist approved, the rough cut watched, the final passing its packaging check. A stage that ends in nothing reviewable gets merged into the next one.
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.
- 7d ago First seen · 125 lines · 80 tokens per session scan A 01e7c6315606
to-tickets is a skill published in the GitHub repository the-sid-dani/second-brain-os (3 stars, last pushed 7d ago), licensed MIT. It adds 80 tokens to every session and 1,642 once invoked, about $0.0003 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-10-17.
Other skills, from other repositories
peer-onboard
A procedure for bringing an outside lead or peer into a shared working setup, including their contact space, records, previous conversations, and ongoing session.
contrib-watch
Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.
issue-match
Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull request there. Reports how many PRs are open, how many of the last N closed ones were actually merged, and which issue to attach to, because a cold PR into a dead queue is a wasted artifact. Triggers…
local-engineer-outreach
An engineer-outreach workflow that manages ongoing conversations with engineering contacts and moves them through planned next steps toward an invitation or call to action.
outbound-gate
Gate for any outbound message before it leaves: pull request or issue comment, DM, invite, post, email. Use before sending to check facts, tone, platform rules, registry status and AI-slop, and to block text that fails.