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 krzysztofsurdy/code-virtuoso --skill ticket-writergit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/ticket-writer)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/ticket-writer"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/ticket-writer/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/krzysztofsurdy/code-virtuoso/ticket-writer"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/ticket-writer.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.00064 | $0.02329 |
| Opus 5.5 | $0.00026 | $0.00932 |
| Sonnet 5.5 | $0.00013 | $0.00466 |
| Haiku 4.5 | $0.00006 | $0.00233 |
Grade A, and why
ticket-writer 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket writer
Pick the right ticket type, then fill in only the fields that type needs. A story is not a bug, and an epic is not an initiative. Each type has its own audience, scope, and definition of done. Mixing them produces vague tickets that nobody can act on and that bloat the backlog.
Core Principles
| Principle | Meaning |
|---|---|
| Type drives structure | The type decides the required fields. Never use a single template for everything |
| Outcomes over outputs | Describe the change the work creates, not the activity performed |
| Small enough to finish | Stories and subtasks fit a sprint; epics fit a quarter; initiatives span multiple quarters |
| Testable acceptance | Every story, subtask, and bug has acceptance criteria that a reviewer can verify |
| Context, not prose | Prefer tables, lists, and labelled sections over paragraphs, because readers skim |
| One ask per ticket | If a ticket has two unrelated goals, split it |
| Vertical slices | A story or subtask should be a thin, demoable path through every layer, not one layer of a feature, and should name the tickets that block it. See spec-driven-development references/slicing.md |
Type hierarchy and selection
Tickets form a hierarchy. Pick the highest level where the work still has a single, coherent purpose.
Initiative (multi-quarter strategic outcome)
Epic (quarter-scale goal, one product area)
Story (sprint-scale user-visible value)
Subtask (implementation slice of a story)
Bug (defect against current behaviour)
Issue (anything else - chore, spike, question)
When to use each type
| Type | Audience | Scope | Typical duration | Key question |
|---|---|---|---|---|
| Initiative | Execs, product leadership | Cross-team strategic goal | 1-4 quarters | What outcome do we want for the business or users? |
| Epic | Product, engineering, design | Single product area, multiple stories | 1 quarter | What capability or experience are we delivering? |
| Story | Dev team, QA, PM | One user-facing change | Fits in a sprint | As a [user], what can I now do? |
| Subtask | One developer | Technical slice of a story | Hours to 1-2 days | What specific implementation step does this cover? |
| Bug | Dev team, QA | A deviation from intended behaviour | Fix-sized | What is broken, and how do I reproduce it? |
| Issue | Dev team | Chore, spike, question, tech debt, docs | Variable | What needs attention that isn't user-facing work? |
What ships with it
6 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.
- yesterday Changed · -2 lines da86f173dbe5
- 4d ago Changed · +1 lines 01e8a8e756d6
- 6d ago Changed · -63 tokens per session 638bd7f86b42
- 1mo ago First seen · 183 lines · 127 tokens per session scan A 420c83300184
ticket-writer is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 2,329 once invoked, about $0.0003 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
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
survey
A project-discovery workflow that creates `.claude/context.md`, a shared file describing the project's purpose, design, constraints, and measures of success.
hermes-overnight-autonomy
Use for unattended Hermes continuity and watchdogs.
dev-plan
Full development planning pipeline. Orchestrates a team of agents (researcher, prd-writer, software-architect, project-planner, issue-estimator) to take a project idea from concept to sprint-ready issues.
github-issues
Create, search, triage, and manage GitHub issues. Each section shows gh first, then the curl fallback.