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 dsnger/dev-workflow-kit --skill ticketgit clone --depth 1 https://github.com/dsnger/dev-workflow-kitWrote 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/dsnger/dev-workflow-kit/ticket)<a href="https://agentmods.dev/skills/dsnger/dev-workflow-kit/ticket"><img src="https://agentmods.dev/badge/skills/dsnger/dev-workflow-kit/ticket/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/dsnger/dev-workflow-kit/ticket"><img src="https://agentmods.dev/badge/skills/dsnger/dev-workflow-kit/ticket.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.00089 | $0.04005 |
| Opus 5.5 | $0.00036 | $0.01602 |
| Sonnet 5.5 | $0.00018 | $0.00801 |
| Haiku 4.5 | $0.00009 | $0.00400 |
Grade A, and why
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 yesterday.
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
88% identical to ticket — 47 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ticket
Overview
The entrance for work that stays inside what is already approved. A report goes in; a ticket file
comes out at docs/superpowers/tickets/<YYYY-MM-DD>-T<n>-<slug>.md, committed on its own. The
ticket is the plan for its fix: it quotes the commitment the fix stays inside, records the
evidence, and carries the brief. It opens no spec and no Gate-A cycle, because the commitment it
stays inside was already reviewed. A change to a commitment is not a ticket: it goes to
dev-workflow:intake.
Done when one ticket file is committed on its own and its hand-off or questions are printed — or nothing is written and the intake hand-off is printed.
Target model: Claude via Claude Code.
This skill is a prompt artifact and follows the checklist in docs/prompt-standards.md.
This skill is one file on purpose. A route file behind a prose pointer is not re-read after context compaction (finding F7, PR #60), so every step lives here. A single short invocation is less exposed to compaction than a multi-turn route; that is a reason, not evidence.
When to use
- A bug, a regression, a robustness gap or a wording defect is reported, and the expected behaviour
is already written down in a story criterion, a spec section, an
AGENTS.mdinvariant or adocs/PRD.mdfeature-map row. - An improvement is requested that stays inside such a commitment.
list: see what is open.T-<n> <state>: move a ticket.
Not for new behaviour or a changed commitment (that is dev-workflow:intake), and not for hardening
a review finding (that is dev-workflow:harden-finding, which keeps owning the finding).
Invocation
| Form | Does |
|---|---|
/dev-workflow:ticket <text> or <path to evidence> |
captures a new ticket (Flow) |
/dev-workflow:ticket list |
prints the buckets (§ list) |
/dev-workflow:ticket T-<n> |
shows that ticket |
/dev-workflow:ticket T-<n> <state> [reason or commit] |
changes its state (§ State changes) |
Any other argument shape: stop and ask which form was meant, because guessing would write a file nobody asked for. A change to a field other than the state is an ordinary edit of the file.
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.
- yesterday First seen · 274 lines · 89 tokens per session scan A 516b2559061c
ticket is a skill published in the GitHub repository dsnger/dev-workflow-kit (6 stars, last pushed 2d ago), licensed MIT. It adds 89 tokens to every session and 4,005 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to ticket, differing in 47 lines, and is treated as a copy.
Other skills, from other repositories
ring:dispatching-workflows
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
ring:managing-dev-cycle
Managing an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
ring:planning-large-features
Planning the 8-gate Large Track pre-dev workflow (research, PRD, feature map, TRD, API contract, data model, dependency map, plan) with per-gate human approval. Use for features 2+ days that add dependencies, data models, multi-service integration, or new architecture. Skip for small features (use…
ring:planning-small-features
Planning the lightweight 4-gate Small Track pre-dev workflow (research, PRD, TRD, plan) with human approval and state tracking at each gate. Use for features under 2 days that reuse existing patterns and add no new dependencies, data models, or services. Skip for larger or complex features — use…