Borrowing it
Nothing to install: this file belongs to fulminate-io/knowledge-mcp. 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/fulminate-io/knowledge-mcp/main/.claude/skills/ticket/SKILL.mdgit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/ticket)<a href="https://agentmods.dev/skills/fulminate-io/knowledge-mcp/ticket"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/ticket/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/fulminate-io/knowledge-mcp/ticket"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/ticket.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.00053 | $0.01243 |
| Opus 5.5 | $0.00021 | $0.00497 |
| Sonnet 5.5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TICKET — the record of what the user needs
What a ticket is for
The ticket answers one question: what does the user need, in the user's words, precisely enough that a researcher can validate it, a planner can prefill for it, a reviewer can audit against it, and a code reviewer can judge the result by it. Building the wrong thing correctly is the ticket's failure; every other failure has a later audit.
The draft schema
Every non-trivial ticket carries these sections, in this order:
- Goal, in the user's words, verbatim where the user stated it.
- Requirements: one line each, each an OBSERVABLE of the finished system ("a create with a label the tracker already holds reuses it and issues no create call"), never a description of code. Number them; the prefill's what-to-test list and the code review key on the numbers. A STRUCTURAL requirement, a shape that must or must never appear in source ("no unbounded body read on a fetch path", "every connection read pages to exhaustion"), is written as a CHECK requirement: it names the corpus check that will enforce it, existing (by id) or to be authored, with the bad shape and the near-miss good shape its fixture pair must vary. A structural requirement carried only as prose is not testable and is not admissible.
- Premises: every fact the ticket rests on, each labeled with provenance:
user-stated,reproduced(with the command and output on the research node),source-read(file:line, opened), orunverified. A ticket with anunverifiedpremise is a draft and cannot leave draft status. - In scope: the surfaces the work touches, the decided design, the verbatim quotes of every load-bearing rule the user gave.
- Out of scope: the temptations, the shapes the user rejected (verbatim), the adjacent work deliberately excluded, the "while we're in there" cleanup.
- Direction: how the user wants it done, where the user stated a preference; recorded as a preference, never inflated into a requirement.
- Landing: the branch or PR the work lands on and anything it must land after.
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 Changed · +2 lines d17d72b3093d
- 1mo ago First seen · 102 lines · 53 tokens per session scan A 67012bf89367
ticket is a skill published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,243 once invoked, about $0.0002 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-09-07.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.