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/fetch-ticketnpx skills add eai-org/agent-toolkit --skill fetch-ticketgit clone --depth 1 https://github.com/eai-org/agent-toolkitWhat 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 | $0.00043 | $0.01936 |
| Opus 5 | $0.00022 | $0.00968 |
| Sonnet 5 | $0.00009 | $0.00387 |
| Haiku 4.5 | $0.00004 | $0.00194 |
Grade A, and why
fetch-ticket scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Download each straight to disk (e.g. `curl -fSL <url> -o <file>`); never route one as inline How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Fetcher
Fetch only — no analysis, requirements, or planning. Output is a self-contained .TICKET.md.
Source & access
Identify the tracker from the input (URL host, or id shape) and fetch through the matching MCP
server — e.g. Azure DevOps MCP for ADO work items, Atlassian MCP for Jira issues, GitHub
MCP / gh for GitHub issues. Use whichever equivalent tools are connected; tool name prefixes
vary by config. Resolve once any handle the MCP needs (e.g. Atlassian cloudId, ADO project) and
reuse it. If the input is ambiguous, ask the user — don't guess. If no matching MCP is connected:
a public ticket may be scraped from its URL as a fallback (you may still suggest installing the
matching MCP when it would do the job better); a private one can't — the URL returns a login page,
not the ticket — so stop and tell the user to install and authenticate the matching MCP server,
then re-run.
Your task
- Resolve the input. Accept a full ticket URL or a bare id/key; extract the identifier. If the
tracker uses a key prefix (e.g.
XX-1234), keep it; otherwise use the bare number. If the input is unrecognizable, ask. - Fetch the ticket. Get the work item/issue with its full field set, comments inline, and related links/relations expanded. Capture everything the ticket carries — don't pre-filter to a fixed set of fields. Convert whatever rich-text form you get (HTML, ADF, …) to clean Markdown.
- Pick a slug. Short kebab-case slug, 3–5 words, from the title/summary — greppable, don't overthink it.
- Decide the output directory. First resolve the project's planning directory (e.g.
.agents/plans/) — follow the project's/user's convention for where plans live. Inside it, first match wins:- Re-fetch — the ticket already has a plan directory or flat
.TICKET.md: suggest the next<id>-<slug>-v2,-v3, … name beside it (directory or filename alike) — never overwrite; history per re-fetch is kept on purpose. - Existing family — an ancestor (parent/epic, nearest first) has a plan directory
(
<ancestor-id>-*, hyphen included; confirm via its.TICKET.mdthat it's really that ancestor's; latest-vNwhen several), or a group directory's## Ticket setlists this ticket or a sibling: write flat into it (<dir>/<id>-<slug>.TICKET.md) and update the## Ticket setsections per multiple-tickets.md. - Otherwise — a new
<id>-<slug>/subdirectory.
- Re-fetch — the ticket already has a plan directory or flat
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.
- 2d ago First seen · 159 lines · 43 tokens per session scan A f886a3d506b6
fetch-ticket is a skill published in the GitHub repository eai-org/agent-toolkit (43 stars, last pushed 12d ago), licensed MIT. It adds 43 tokens to every session and 1,936 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gsd-complete-milestone
Archive completed milestone and prepare for next version.
conductor-new-track
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-cleanup
Archive accumulated phase directories from completed milestones.
gsd-extract-learnings
Extract decisions, lessons, patterns, and surprises from completed phase artifacts.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…