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 agentmods add skills/spillwavesolutions/wiki_ticket_sdd/releasenpx skills add SpillwaveSolutions/wiki_ticket_sdd --skill releasegit clone --depth 1 https://github.com/SpillwaveSolutions/wiki_ticket_sddWrote 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/spillwavesolutions/wiki_ticket_sdd/release)<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/release"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/release.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.01760 |
| Opus 5 | $0.00032 | $0.00880 |
| Sonnet 5 | $0.00013 | $0.00352 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
release 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 today.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
A release is worklog work: record a release task first (work-track), and the release leaves frozen artifacts behind — a dated changelog section, a roadmap snapshot, a tag, and a platform release. No per-system code ships with this skill; use the platform's own release tooling.
1. Preconditions
- Clean working tree on the default branch (or a release-prep branch about to merge into it).
- All test suites green locally; CI green on the tip.
- Version lockstep holds: the plugin manifest,
bin/worklog --version, and every plugin skill's frontmatter agree (tests/test_plugin.pyenforces it). - The top CHANGELOG section reads
## X.Y.Z — unreleasedand describes what actually ships. If it doesn't, fix that first — release notes are written as features land, not reconstructed at tag time. When the section is missing or thin,bin/worklog changelog-draft --version X.Y.Zwrites a starting draft from git log since the last tag (markdown on stdout, the commits it excluded on stderr). It is bullets, not release notes: edit the prose before stamping, and read the exclusion list to confirm nothing real was dropped.
2. Stamp
- CHANGELOG: change
— unreleasedto— YYYY-MM-DD(UTC, release date). bin/worklog roadmap-snapshot --name vX.Y.Z-release— the frozen picture of open work at release time. Snapshots are frozen; never regenerate.bin/worklog ia-index— sidecars the new snapshot (stamping itsreleaseand supersede chain), refreshes the inventory, and re-renders Home/Sidebar/Releases-index + publish manifest so the release is navigable. Commitdocs/.index/with the snapshot.bin/worklog trace-check --strict— the pre-release evidence gate: every closed item must trace to a plan, ticket, and PR. Failures block the release; fix the links (worklog link-pr, sidecarrelates_to) or consciously report the gaps to the human — never skip silently.bin/worklog doc-verify --strict— the pre-release citation gate: every document's code citations must resolve at the commit that document was written against. FABRICATED means wrong even in the tree the author had open — a real defect, fix it. DRIFT on a frozen document is expected and does not block; drift oncurrent_design_doc/current_code_walkthroughdoes, because those claim to describe HEAD.unresolvablemeans the stamped commit is not in this clone (see ADR-0008) — report it, never re-check against HEAD.
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.
- today Changed cad0b38c9ec7
- 4d ago First seen · 132 lines · 64 tokens per session scan A fc2ffcbc8487
release is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 1,760 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…