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/pr-descriptionnpx skills add SpillwaveSolutions/wiki_ticket_sdd --skill pr-descriptiongit 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/pr-description)<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/pr-description"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/pr-description.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.00062 | $0.00921 |
| Opus 5 | $0.00031 | $0.00461 |
| Sonnet 5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
pr-description 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
High-quality PR descriptions
Run bin/worklog triggers pr-open. If pr-description is not in the
list, skip this skill — the team opted the event out.
A PR description is a durable design record, useful long after the merge. Write for a smart colleague who has never seen this part of the system. Trivial PRs (typo, one-line fix) may use a short body; everything else follows this structure.
Structure
1. Title
Clear, specific, ticket-linked: #98: ia-render — reader plane write path.
2. The big picture (what we're building, where this PR fits)
Product context in plain language: the platform, the epic/capability this belongs to, the epic broken into a numbered pipeline with this PR marked:
Step 1: ...
Step 2: ...
Step 3: ... <== THIS PR
Step 4: ...
Define domain terms on first use (fold, ledger, sidecar, MCP, ...).
3. Who actually calls this? / runtime context
The real caller and execution model: human + AI assistant, background job, hook, webhook, UI? What surrounding system runs it? Does anything run automatically or is confirmation gated? Security/permission notes (e.g. "forwards the user's real token").
4. The problem this PR solves
Concrete, numbered pain points that exist today. Why the naive approach fails and what correct behavior must be. The reader should feel the pain the PR eliminates.
5. What this PR actually does (scope)
The ticket's exact ask, then confirmation the PR delivers precisely that. Explicit in-scope / out-of-scope boundaries.
6. What exactly was added / changed
File by file (or component by component): path, what it contains, why it was designed that way (especially non-obvious decisions), implementation constraints (framework-free, no schema drift, deterministic output, ...). Describe new tools/prompts/schemas clearly.
7. The sequence / flow the code enforces
For multi-step processes (especially ones an AI must follow): exact ordered steps, decision points, confirmation gates, error handling, and explicit "never do X" rules.
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 6b06346be539
- 5d ago First seen · 97 lines · 62 tokens per session scan A 35b963e49e72
pr-description is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 921 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…