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 TweekFawkes/prompts --skill newticketgit clone --depth 1 https://github.com/TweekFawkes/promptsWrote 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/tweekfawkes/prompts/newticket)<a href="https://agentmods.dev/skills/tweekfawkes/prompts/newticket"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/newticket/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/tweekfawkes/prompts/newticket"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/newticket.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.00169 | $0.02468 |
| Opus 5 | $0.00084 | $0.01234 |
| Sonnet 5 | $0.00034 | $0.00494 |
| Haiku 4.5 | $0.00017 | $0.00247 |
Grade A, and why
newticket 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 10d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/newticket — Author one new backlog ticket
Run this in your main checkout (the one where main is checked out), before creating a worktree for the work.
You are creating exactly ONE new ticket file in z_tickets/open/ based on the brief in the user message that invoked this skill. Treat that brief as $BRIEF for the rest of this skill.
If the user message contains no brief, ask the user for one and stop. A brief can be one line or a few paragraphs — both are fine.
Use --spec-only when the ticket is genuinely being deferred — backlog for later, not work to start now.
Authoritative paths
- Project root: the current working directory.
- Open tickets (your destination):
z_tickets/open/ - Closed tickets (for naming + tone reference):
z_tickets/closed/ - Onhold tickets (also reserved):
z_tickets/onhold/ - Ticket template:
z_tickets/examples/_TEMPLATE.md - Project conventions: read
CLAUDE.mdat the repo root if present, and follow it.
Operating principles (must follow)
- Plan, don't implement. Your only output is a single Markdown file describing the work. No code edits. No tests. No commits. The
/doworkskill does the implementation later. - Smallest scope that makes sense. A ticket should be roughly one PR's worth of work. If
$BRIEFdescribes more than that, write the smallest first slice and note follow-ups in "Out of scope". - Concrete over vague. The "Scope" section should name files / routes / components / tests where you can. Vague tickets produce speculative diffs.
- Match the project's existing style. Glance at 2-3 closed tickets to calibrate tone, length, and section conventions before drafting.
- One ticket per invocation. If
$BRIEFcovers two unrelated pieces of work, pick the one the user clearly meant first and write only that. Mention the second as a TODO in your final summary so the human can re-invoke.
Required workflow
1. Refresh the checkout to the latest main
The spec must be written against current code, so bring the checkout up to date first:
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.
- 10d ago First seen · 143 lines · 169 tokens per session scan A 11da3d409f62
newticket is a skill published in the GitHub repository TweekFawkes/prompts (2 stars, last pushed 1mo ago), licensed Unlicense. It adds 169 tokens to every session and 2,468 once invoked, about $0.0008 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
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.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.