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.00069 | $0.02981 |
| Opus 5 | $0.00034 | $0.01491 |
| Sonnet 5 | $0.00014 | $0.00596 |
| Haiku 4.5 | $0.00007 | $0.00298 |
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 10d 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ticket Workflow
End-to-end workflow that takes a ticket ID and drives it through analysis, codebase investigation, planning, TDD implementation, committing, and PR creation. Adapts to your stack via an interactive supplement created on first run.
Phase 0: Environment Supplement
Before anything else, check for a supplement file stored alongside this skill (e.g., .supplement.md in the skill directory).
If supplement exists
Read the file and load all $VARIABLE values for use throughout the workflow.
If supplement is missing
Run an interactive setup. Present an interactive prompt (or the platform's equivalent) for each question, wait for the answer, then proceed to the next. Save all answers to a supplement file stored alongside this skill (e.g., .supplement.md in the skill directory).
Questions to ask (see supplement reference for full details):
- Ticket system - GitHub Issues / GitLab Issues / Jira / Linear / Other? Integration tool name for fetching tickets?
- Version control - Bitbucket / GitHub / GitLab? CLI tool (
gh,glab)? Main branch name? - Error tracking - Bugsnag / Datadog / Sentry / none? Integration tool name?
- Logging - CloudWatch / Datadog / ELK / Grafana / none? Tool access or manual paste?
- Database - ORM (ActiveRecord / Doctrine / Eloquent / Prisma / TypeORM / none)? Read-only query command?
- CI/CD hooks - Pre-commit hooks to skip? (e.g.,
SKIP=lint,test git commit) - Testing framework - Go test / Jest / PHPUnit / pytest / RSpec / other? TDD style preference (London / Chicago)?
- Architecture - Monolith / microservices? Admin panel? API layer (REST / GraphQL / both)?
- PR conventions - Branch naming pattern? Commit message format?
After saving, confirm: "Supplement saved. You can edit it anytime at the supplement file path or delete it to re-run setup."
Delegation Strategy
This workflow can use a multi-agent team when available. The coordinating agent delegates to specialized sub-agents for parallel investigation.
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.
- 10d 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 (21 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 2,981 once invoked, about $0.0003 per session on Opus 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.
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.
friction-log
File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.
jira
Jira integration — view issues, generate branches, create tickets, transition status. Use when: user mentions Jira ticket key (XX-123), says /jira, wants to create branch from ticket, create a new ticket, or update Jira status. Not for: GitHub issues (use issue-analyze).
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".