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/create-a-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/create-a-ticket)<a href="https://agentmods.dev/skills/fulminate-io/knowledge-mcp/create-a-ticket"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/create-a-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.00060 | $0.00989 |
| Opus 5 | $0.00030 | $0.00495 |
| Sonnet 5 | $0.00012 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
create-a-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 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.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CREATE-A-TICKET — what must be true before a ticket exists
THE RESEARCH GATE (absolute, blocking)
NO TICKET IS CREATED until, in order:
- A RESEARCHER PASS answered: every open question the ticket would carry, the high-level design (which existing seams and idioms the work binds to), and — for a defect — the root cause OBSERVED at the mechanism level (in source or reproduction). A mechanism nobody observed enters the ticket labeled "unproven" or the ticket ships symptom-only; your own inference gets the same bar as any inbound claim. A live investigation already running on the same mechanism IS the researcher pass — the ticket waits for it.
- A PRIOR-DECISION SWEEP over every touch point the ticket names, checking the proposed design against each recorded decision.
- CONFLICTS ROUTED to the user as TICKET-GAPS before the ticket freezes — a design/decision disagreement is never resolved silently in either direction.
- THE DECISION RECORD UPDATED with the user's ruling in the same breath as the ticket — a ticket contradicting a standing decision record is a landmine.
- FOR DEFECT TICKETS: A ROOT-CAUSE CHECK MINTED FIRST — a check capturing the root-cause class exists in the checks graph, authored to the storing bar (fired on a bad fixture, silent on a good one; ast_pattern where mechanical, llm_only where it needs judgment — llm_only is exclusive with fixtures). A root cause that genuinely cannot be a check is surfaced to the user WITH the ticket as an explicit exception — never self-exempted.
The one exception: a symptom-only ticket for an ACTIVE INCIDENT may be created immediately to carry mitigation state — its mechanism section says UNKNOWN, the researcher pass amends it before any implementation dispatch, and the root-cause check is minted with that amendment.
The tell you are about to violate the gate: a ticket description carrying your own unverified mechanism as fact, an open question left for the planner, or a design no researcher checked against the decision graph.
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 · 80 lines · 60 tokens per session scan A 9a6e3063177e
create-a-ticket is a skill published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 3d ago), licensed Apache-2.0. It adds 60 tokens to every session and 989 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-09-04.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.