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-deliverygit 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-delivery)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/ticket-delivery"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/ticket-delivery/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-delivery"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/ticket-delivery.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.00050 | $0.03402 |
| Opus 5.5 | $0.00020 | $0.01361 |
| Sonnet 5.5 | $0.00010 | $0.00680 |
| Haiku 4.5 | $0.00005 | $0.00340 |
Grade A, and why
ticket-delivery 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 4d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Workflow
This workflow takes a ticket ID and drives it through analysis, codebase investigation, planning, TDD implementation, committing, and PR creation. Saved config, created by an interactive setup on first run, adapts it to your stack.
Phase 0: Environment config
Before anything else, load the saved choices for this workflow from the layered Code Virtuoso config. They live under the ticket-delivery namespace, never next to this skill, so they survive updates and reinstalls. See setup questions for the key list, the read recipe, and the legacy mapping.
- Resolve layers. Read, in order, the user file (
$CODE_VIRTUOSO_CONFIG_HOME/config.json, else${XDG_CONFIG_HOME:-~/.config}/code-virtuoso/config.json),<project root>/.code-virtuoso/config.json, and<project root>/.code-virtuoso/config.local.json. Later files win, objects merge key by key, missing files are normal. Use the mergedticket-deliveryobject for the rest of the workflow. Keys it does not set fall back to the defaults in the setup reference. - Migrate legacy files. If the namespace is empty in every layer, look for an old
.supplement.md(locations and the key mapping are in the setup reference). Import its values to the user layer, then tell the user the old file can be deleted. Leave it in place. - Run setup for missing values. If required values are still missing, run the interactive setup. Setup runs in the main session only. When running as a sub-agent, never ask the user: use the defaults and end the report with "Defaults used for: . Run ticket-delivery setup to save them."
- Write to the right layer. Each question is tagged
scope: userorscope: project. Save the answer to that layer, changing only theticket-deliverykeys you own and keeping every other key. After writing, show the user the path of each file written. - Offer the pointer line. Offer to add
Shared tool decisions: .code-virtuoso/config.jsonto the projectAGENTS.md(orCLAUDE.md). Add it only if the user agrees.
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.
- 4d ago Changed · +4 lines · -19 tokens per session 61bd38ed8f6e
- 1mo ago First seen · 375 lines · 69 tokens per session scan A 522037bdba52
ticket-delivery is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 3,402 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-08-30.
Other skills, from other repositories
github-issues
Create, search, triage, and manage GitHub issues. Each section shows gh first, then the curl fallback.
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.