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 d-mariano/spicyclaude --skill writing-ticketsgit clone --depth 1 https://github.com/d-mariano/spicyclaudeWrote 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/d-mariano/spicyclaude/writing-tickets)<a href="https://agentmods.dev/skills/d-mariano/spicyclaude/writing-tickets"><img src="https://agentmods.dev/badge/skills/d-mariano/spicyclaude/writing-tickets/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/d-mariano/spicyclaude/writing-tickets"><img src="https://agentmods.dev/badge/skills/d-mariano/spicyclaude/writing-tickets.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.00123 | $0.00768 |
| Opus 5 | $0.00062 | $0.00384 |
| Sonnet 5 | $0.00025 | $0.00154 |
| Haiku 4.5 | $0.00012 | $0.00077 |
Grade A, and why
writing-tickets 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 12d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Authoring
Pick the issue type that fits the work, then read the sub-file for the template and type-specific guidance before drafting.
Issue Types
- Epic — multi-sprint features, typically born from a PRD. Use on request. See epic.md
- Spike — research or PoC work that may produce more issues. See spike.md
- Story — user-facing features and behaviour changes. See story.md
- Task — technical or operational work. See task.md
- Bug — defects. See bug.md
Definitions
- Acceptance Criteria: observable behaviour or deliverables. Testable from the outside.
- Engineering Notes: how-to. Libraries, patterns, code pointers, citations.
Steps
- ALWAYS use the template from the matching sub-file
- If there are any gaps in the details, push back with clarifying questions before drafting
- Create one or more tickets to capture the work; split when scope spans types
- Always include reference and resource links in Engineering Notes and Summary where applicable
- When referencing code or files, pair the short path with a SHA-pinned repo permalink — mechanics in references/code-references.md. Tickets must stand on their own
- Hard gate: load-bearing content that exists only locally or in this conversation (uncommitted docs, local logs, decisions made in chat) blocks the ticket — commit + permalink, upload + link, or inline it before drafting
- Do not write large chunks of tests or novels
- Communicate effectively and keep it to the point
- Conduct any web searches needed for frameworks in use, unless the usage examples in code are telling enough
- Refer to usage examples and best practices when found
- Research if third-party packages in use already provide required types and explicitly call this out
- If alternative approaches are identified and you have a preference, only mention your preference
- Favour simplicity and elegance
- Cite sources
Output
What ships with it
8 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.
- 12d ago First seen · 46 lines · 123 tokens per session scan A 8e37b5b317df
writing-tickets is a skill published in the GitHub repository d-mariano/spicyclaude (5 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 768 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…