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/design-docsnpx skills add SpillwaveSolutions/wiki_ticket_sdd --skill design-docsgit 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/design-docs)<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/design-docs"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/design-docs.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.00101 | $0.02056 |
| Opus 5 | $0.00051 | $0.01028 |
| Sonnet 5 | $0.00020 | $0.00411 |
| Haiku 4.5 | $0.00010 | $0.00206 |
Grade A, and why
design-docs 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design docs and code walkthroughs
Two live files, one freeze note per release, one rule: generated from the
actual repo, never from memory. The templates live in references/; this
skill is the procedure around them.
Companion skills (required)
When this skill writes an architecture doc, a code walkthrough, or a requirements doc, invoke the
Spillwave documentation suite. Install from
SpillwaveSolutions/spillwave-documentation-marketplace v0.2.1.
Load references/companion-skills.md before either prompt.
| Role | Skill | Version | Rule |
|---|---|---|---|
| Prose | document-specialist |
v3.2.2 | Default voice is STE100. Switch to google-docs-style v1.1.4 only when the user names Google style. Never mix packs. Wireframes belong in this skill's diagram pass. |
| GitHub-safe diagrams | design-doc-mermaid |
v1.1.1 | Default for flowchart, sequence, class, ER, state, C4, and component views. Fenced mermaid in the Markdown. Validate before publish. |
| Leftover UML and wireframes | plantuml |
v1.2.2 | Use case, timing, ArchiMate, Salt wireframes, nwdiag, WBS. Always render PNG or SVG. GitHub wiki does not render PlantUML source. |
Hard bans for prose in both voice packs:
- No em dash.
- Do not start a sentence with So, That, Thus, or Hence.
Artifacts
| File | Kind | Rule |
|---|---|---|
docs/designs/current_design_doc.md |
live | regenerated each release; in-place rewrite is sanctioned (like docs/roadmap.md) |
docs/designs/current_code_walkthrough.md |
live | same |
docs/designs/<DATE>_vX.Y.Z-release.md |
freeze note | tag + git_hash + pointers at the live pair + a short delta from the previous freeze. Frozen. Not a copy of the live pair. |
docs/designs/<DATE>_<NAME>_design_doc.md |
legacy dated | full copies written before the freeze cap. Frozen forever. Never regenerate, never edit. |
docs/designs/<DATE>_<NAME>_code_walkthrough.md |
legacy dated | same |
docs/requirements/<NAME>_srs.md or _prd.md |
ad-hoc | generated on request from requirements-doc-prompt.md. Register with worklog wiki-add. |
What ships with it
4 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 736c0819f482
- 5d ago First seen · 167 lines · 101 tokens per session scan A a6171d58aca4
design-docs is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 2,056 once invoked, about $0.0005 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…