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 rampstackco/claude-skills-pm --skill ticket-authoringgit clone --depth 1 https://github.com/rampstackco/claude-skills-pmWrote 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/rampstackco/claude-skills-pm/ticket-authoring)<a href="https://agentmods.dev/skills/rampstackco/claude-skills-pm/ticket-authoring"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills-pm/ticket-authoring/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/rampstackco/claude-skills-pm/ticket-authoring"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills-pm/ticket-authoring.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.00185 | $0.02385 |
| Opus 5.5 | $0.00074 | $0.00954 |
| Sonnet 5.5 | $0.00037 | $0.00477 |
| Haiku 4.5 | $0.00018 | $0.00238 |
Grade A, and why
ticket-authoring 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 6d 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.
This is a copy
100% identical to ticket-authoring — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Authoring
Turn specs, bug reports, and loose requests into work items someone can pull and start without asking a question. Tracker-agnostic: works in Jira, Linear, GitHub Issues, or your tracker of choice.
When to use
- Turning a PRD or spec into a set of tickets
- Filing a bug that someone else will fix
- Writing a user story with checkable acceptance criteria
- Scoping a spike so it ends in a decision, not a shrug
- Opening an epic with a goal, a metric, and a way to kill it
- Auditing a backlog for tickets that are not ready to pull
- Tagging work items with a capitalization stage for finance
When NOT to use
- Writing the PRD or spec itself (use
pm-spec-writing) - Deciding what ships this quarter (use
roadmap-planning) - Running sprint ceremonies or measuring the team (use
sprint-operations) - Writing up what went wrong after the fact (use
after-action-report) - Handing a whole plan to a coding agent to execute unattended (use
dispatch-authoring)
Required inputs
- The source material: a spec, a bug description, a request, or a conversation
- The ticket type, or enough context to pick one
- The tracker's field set, if it has required custom fields
- The parent epic or story, if one exists
- The capitalization policy, if the team capitalizes software development
If the source is vague, ask before writing. A ticket written around a guess becomes a second ticket later.
The framework: five types, one definition of ready each
A ticket is ready when the person who pulls it can start work without a question. Each type has its own required fields, its own attachments, and its own done test. A field left blank is a question someone will ask in the middle of the sprint.
Every type shares a base: title, type, owner, parent link, labels, and capitalization stage.
Bug
A bug ticket proves the defect exists and defines how to prove it is gone.
- Title.
[area] [symptom] when [trigger]. Example: "Checkout: total shows $0.00 when a promo code is removed." - Repro steps. Numbered. Each step is one action. Someone who has never seen the product can follow them.
- Environment. Build or version, browser or device, account type, data state.
- Observed vs expected. Two separate lines. Never one sentence with "but."
- Current test result. The test that fails today, or "no test covers this."
- Severity and priority. Two fields. Severity is how bad the defect is. Priority is when the team fixes it.
- Regression risk. What else touches this code path.
- QA notes. Edge cases to check beyond the repro.
- Fix verification method. The specific test that proves the fix, by name or by steps.
- Expected test result after fix. What passing looks like.
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.
- references/bug-template.md 3.9 KB
- references/capitalization-guide.md 5.8 KB
- references/definition-of-ready-checklist.md 3.3 KB
- references/epic-template.md 2.4 KB
- references/example-bug-and-story.md 5.8 KB
- references/spike-template.md 2.3 KB
- references/story-template.md 2.8 KB
- references/task-template.md 2.7 KB
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.
- 6d ago First seen · 186 lines · 185 tokens per session scan A ab681d0600e2
ticket-authoring is a skill published in the GitHub repository rampstackco/claude-skills-pm (4 stars, last pushed 7d ago), licensed MIT. It adds 185 tokens to every session and 2,385 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ticket-authoring, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…
roadmap-planning
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next…
ticket-authoring
Write complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub issue, file a bug report, write a user story…
html-ppt-graphify-dark-graph
OpenDesign's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.