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 skills add asteasolutions/ai-toolkit --skill to-ticketsgit clone --depth 1 https://github.com/asteasolutions/ai-toolkitWrote 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/asteasolutions/ai-toolkit/to-tickets)<a href="https://agentmods.dev/skills/asteasolutions/ai-toolkit/to-tickets"><img src="https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/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/asteasolutions/ai-toolkit/to-tickets"><img src="https://agentmods.dev/badge/skills/asteasolutions/ai-toolkit/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.00059 | $0.00726 |
| Opus 5 | $0.00030 | $0.00363 |
| Sonnet 5 | $0.00012 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00073 |
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 9d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
to-tickets
Decompose work into tracer-bullet vertical slices. Write helm's work-tree shapes: _map.md plus one leaf doc per ticket (see helm/references/artifacts.md if present).
Publish policy
- Always write local under
.scratch/<goal-slug>/— this is the program counter. - Also mirror to GitHub only when the user asks for GitHub, or already pointed at an issue URL/id. If
docs/agents/issue-tracker.mdexists, follow its GitHub conventions for that mirror. - Never skip the local write. Never ask which tracker after a local-only run.
Process
1. Gather context
Work from the conversation. If the user passes a reference (spec path, issue number/URL), fetch and read it.
2. Explore (optional)
If needed, explore the codebase. Prefer any domain vocabulary the repo already has. Look for prefactoring — make the change easy, then make the easy change. Prefactoring is its own ticket, done first.
3. Draft vertical slices
Each ticket:
- Cuts a narrow but complete path through every layer it touches (schema, logic, interface, tests) — vertical, not horizontal
- Is demoable / verifiable on its own
- Fits in one fresh context as one change
Give each ticket blocking edges — tickets that must finish before it starts.
Wide refactors (one mechanical change with huge blast radius) are the exception: sequence as expand → migrate batches → contract, not forced tracer bullets.
4. Quiz the developer
Present a numbered list: Title · Blocked by · What it delivers. Ask granularity, edges, merge/split. Iterate until approved.
5. Write local artifacts
_map.md— overarching intent + ordered task list with status and blockers:
# <goal title>
## Intent
<overarching what + why>
## Tasks
1. [pending] <task-slug>
2. [pending] <task-slug> — blocked by: 1
- One leaf doc per ticket at
.scratch/<goal-slug>/<task-slug>.md— Intent only at creation (Plan comes later when that leaf is planned):
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.
- 9d ago First seen · 77 lines · 59 tokens per session scan A 733997bb4f30
to-tickets is a skill published in the GitHub repository asteasolutions/ai-toolkit (5 stars, last pushed 8d ago), licensed MIT. It adds 59 tokens to every session and 726 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…