Borrowing it
Nothing to install: this file belongs to stevesolun/ctx. 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/stevesolun/ctx/main/.agents/skills/to-tickets/SKILL.mdgit clone --depth 1 https://github.com/stevesolun/ctxWrote 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/stevesolun/ctx/to-tickets)<a href="https://agentmods.dev/skills/stevesolun/ctx/to-tickets"><img src="https://agentmods.dev/badge/skills/stevesolun/ctx/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/stevesolun/ctx/to-tickets"><img src="https://agentmods.dev/badge/skills/stevesolun/ctx/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.00037 | $0.00303 |
| Opus 5.5 | $0.00015 | $0.00121 |
| Sonnet 5.5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
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 1mo 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.
What it actually says
Create tickets
Read the source plan, spec, issue, or conversation and inspect enough of the repository to avoid fictional boundaries. Use the project's established domain language and preserve relevant architectural decisions.
Prefer narrow vertical slices that deliver observable behavior and can be verified independently. Size work for the actual team and risk rather than a fixed context-window rule. Use horizontal or mechanical slices when the change cannot remain coherent vertically.
Model only real blocking edges. Tickets without blockers form the available frontier and may proceed concurrently. For a broad compatibility migration, consider an expand–migrate–contract sequence so intermediate states remain usable.
Each ticket should communicate:
- the behavior or outcome it delivers;
- concrete acceptance criteria;
- genuine dependencies;
- relevant constraints or source references; and
- scope boundaries when adjacent work is easy to confuse.
Use the ticket format when the destination has no stronger convention. Avoid brittle line numbers and implementation recipes unless the ticket is intentionally mechanical.
Present a draft when granularity or dependencies remain uncertain. Publish or write tickets only when requested and authorized, following the configured tracker's native dependency model. Do not alter a parent item or apply workflow labels unless that action is part of the request.
What ships with it
2 files 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.
- 1mo ago First seen · 38 lines · 37 tokens per session scan A c8d4662aebc0
to-tickets is a skill published in the GitHub repository stevesolun/ctx (589 stars, last pushed 11d ago), licensed MIT. It adds 37 tokens to every session and 303 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
operator-scorecard
Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and failed; push ranks push impact.
github-monitor
Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker.
heartbeat
Ambient fleet-health check that surfaces anything worth attention (default), or an on-demand priority brief - the 3 things to focus on, why now, and what moved (var=brief).
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
idea-pipeline
Execution-gap audit - cross-references the startup idea backlog against shipped skills, prototypes, and cross-repo PRs, surfacing the top 3 ideas to build next by narrative and operator fit.
strategy-builder
Draft STRATEGY.md from a goal - read the operator's brief (goal, repo, links) plus the repo README and memory, then write a tight north-star/priorities/audience/constraints strategy.