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/eai-org/agent-toolkit/review-ticketnpx skills add eai-org/agent-toolkit --skill review-ticketgit clone --depth 1 https://github.com/eai-org/agent-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/eai-org/agent-toolkit/review-ticket)<a href="https://agentmods.dev/skills/eai-org/agent-toolkit/review-ticket"><img src="https://agentmods.dev/badge/skills/eai-org/agent-toolkit/review-ticket.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.1 | $0.00039 | $0.02656 |
| Opus 5 | $0.00019 | $0.01328 |
| Sonnet 5 | $0.00008 | $0.00531 |
| Haiku 4.5 | $0.00004 | $0.00266 |
Grade A, and why
review-ticket 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review ticket
A pre-pickup triage glance: read a ticket — or a set of tickets forming one feature — usually before anyone has started it, and decide whether it can be picked up or something must be clarified first. The output briefs the developer on the feature and lists the questions worth asking whoever owns the requirements.
Input
- Local ticket document(s): a single
.TICKET.md, several, a ticket-set directory, or a.TICKET.mdwhose## Ticket setsection lists siblings. - One or more ticket URLs or bare ids/keys: delegate — even for a single one — to a subagent that invokes fetch-ticket, so the tickets land on disk without the fetch bloating this session's context, then review the local files.
If the input is ambiguous or unrecognized, ask rather than guess.
Set mode applies to multiple tickets, a set directory, or a .TICKET.md listing a
## Ticket set. For a lone member file whose intended scope isn't obvious from the request, ask
whether to review the whole set or just that ticket.
Read the materials
Read the input ticket file(s), visually inspecting the downloaded images and design frames — they are part of the spec and often where the gaps hide.
Widen only on demand. When the input already tells the feature clearly — the journey, the why, what each ticket delivers — review it as-is: reading beyond the input is never a required step. Settle a specific doubt as cheaply as possible, and only to answer it:
- first, material already on disk: set siblings, a parent feature/epic, designs — a technical ticket's journey often lives in its parent or a sibling;
- remotely, only for what is still missing: a design inspected through its tool's MCP, a related ticket deep-dived from the ticket file's shallow related list (title, status, type), a missing parent fetched through the same fetch-ticket subagent (its family routing lands it flat in the set directory).
Unsure the extra context is worth it? Ask. Stop once the doubt is answered; never recurse the related-ticket graph — except to kill a candidate question (see the question bar). Context never widens scope: the review covers only the input tickets, never a parent's other children.
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 · 198 lines · 39 tokens per session scan A 36fcaf8e54a2
review-ticket is a skill published in the GitHub repository eai-org/agent-toolkit (43 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 2,656 once invoked, about $0.0002 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
persona-author
Author or improve an ADD-method persona file (a .add/personas/ slug.md) — the project-fit requirements LENS the ADD engine validates and the design/build/verify/advisor surfaces load. Use when adding a domain expert to the ADD roster, when the add-worker persona mode must DRAFT a persona because none fits the task…
wikispec-wiki
This skills instructs the agent how to maintain the knowledge base in the wiki. Use it when you want to ingest documents or query the wiki.
wikispec-propose
Create specs and designs for a new change. Use this when you need to specify a new change or continue to work on the specification of an existing change.
wikispec-apply
Use the task list for the change to implement the actual change.
wikispec-archive
Drive the agent through the full archive step for a wikispec change. You will use the wikispec tool which is a binary in the path, no need to install anything.
wikispec-plan
Create a tasks list to prepare for the implementation of a change. Use this before implementation to understand what needs to be done.