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 laurigates/claude-plugins --skill ticket-drafting-guidelinesgit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/ticket-drafting-guidelines)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/ticket-drafting-guidelines"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/ticket-drafting-guidelines/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/laurigates/claude-plugins/ticket-drafting-guidelines"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/ticket-drafting-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.02107 |
| Opus 5.5 | $0.00017 | $0.00843 |
| Sonnet 5.5 | $0.00008 | $0.00421 |
| Haiku 4.5 | $0.00004 | $0.00211 |
Grade A, and why
ticket-drafting-guidelines 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 18d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Drafting Guidelines
Expert guidance for drafting clear, concise, and well-structured tickets for GitHub issues, pull requests, and technical documentation.
When to Use This Skill
| Use this skill when... | Use google-chat-formatting instead when... |
|---|---|
| Drafting a GitHub issue, bug report, or feature request with What/Why/How structure | Posting a status update or announcement to a Google Chat channel |
| Writing a PR description or technical ticket with reference links | Converting Markdown headers and bold to Google Chat's single-asterisk syntax |
| Structuring a refactoring task or migration plan with concrete steps | Reformatting meeting notes or release notes for chat consumption |
| Wording the body text — What/Why/How sections, tone, reference links | Use git-plugin:github-issue-writing for the GitHub issue artifact itself: [Type] Component: title format, bug/feature templates, gh issue create |
Core Expertise
- Structured Format: What/Why/How organization for clarity
- Concise Writing: Brief descriptions with reference links
- Markdown Standards: Proper formatting and link syntax
- Positive Framing: Affirmative language without negative phrasing
- Neutral Tone: Factual communication without claims or estimates
- Reference Integration: Links to official documentation
Ticket Structure
Main Headings
Every ticket uses three primary sections:
## What
[Concise description of the subject]
## Why
[Context and motivation]
## How
[Implementation approach or resolution steps]
What Section
Purpose: Describe the subject clearly and concisely.
Guidelines:
- State what the ticket addresses in 1-3 sentences
- Include relevant technical terms
- Link to related issues or PRs using
[#123](URL)format - Reference official documentation where applicable
Example:
## What
Add support for TypeScript configuration in the build pipeline. This enables type checking during CI/CD runs and improves code quality. Related to [#456](https://github.com/owner/repo/issues/456).
See [TypeScript compiler options](https://www.typescriptlang.org/tsconfig) for configuration reference.
What ships with it
1 file 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.
- 18d ago Changed · -81 lines 863a37b6ab70
- 1mo ago First seen · 429 lines · 42 tokens per session scan A 07db14544d48
ticket-drafting-guidelines is a skill published in the GitHub repository laurigates/claude-plugins (59 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 2,107 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-03.
Other skills, from other repositories
delegation-brief
Before delegatetask: brief the subagent, then verify it.
work-ledger
Multi-day or multi-session work: a ledger that survives.
ticket-delivery
End-to-end ticket workflow from analysis through investigation, planning, TDD implementation, commits, and PR creation, adapted to your setup by saved config. Use when starting work on a ticket or implementing a feature from ticket to PR.
backlog-compiler
Converts a PRD, ticket, or feature description into a .code-virtuoso/loop/backlog.json plan sized and ordered for autonomous loop execution. Use when preparing work for the iteration-loop skill, turning a written ticket into a loop-ready backlog, or when asked to turn a spec into a backlog.
morning-brief
Operator's read-only morning view of the current GitHub repo in one pass: open counts per queue label, merge-ready PRs, parked decisions with their RECOMMENDED lines, loop-lane telemetry freshness, per CI lane the week's failures by class, limit stops, restarts and turn headroom, and model usage per activity and…
spec-driven-development
Turns an approved idea or ticket into spec, plan, and task files saved in the repo, then executes them one task at a time with a progress log. Use to write a spec, plan a feature, break work into tasks, or resume multi-session work.