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/integration-guidenpx skills add SpillwaveSolutions/wiki_ticket_sdd --skill integration-guidegit 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/integration-guide)<a href="https://agentmods.dev/skills/spillwavesolutions/wiki_ticket_sdd/integration-guide"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/wiki_ticket_sdd/integration-guide.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.00099 | $0.01418 |
| Opus 5 | $0.00049 | $0.00709 |
| Sonnet 5 | $0.00020 | $0.00284 |
| Haiku 4.5 | $0.00010 | $0.00142 |
Grade A, and why
integration-guide 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration guide
Eleven systems each have a dedicated integration guide, published on the wiki and mirrored locally. This skill's job is to find the right one and follow it — not to carry integration knowledge itself.
1. Match the name to a canonical key
| Canonical key | Aliases | Wiki page | Local fallback file |
|---|---|---|---|
superpowers |
Superpowers | Integration-Superpowers |
docs/integrations/fallback-superpowers.md |
gsd |
GSD, Get Shit Done | Integration-GSD |
docs/integrations/fallback-gsd.md |
speckit |
SpecKit, Spec Kit | Integration-SpecKit |
docs/integrations/fallback-speckit.md |
openspec |
OpenSpec | Integration-OpenSpec |
docs/integrations/fallback-openspec.md |
jira |
Jira, Atlassian Jira | Integration-Jira |
docs/integrations/fallback-jira.md |
confluence |
Confluence, Atlassian Confluence | Integration-Confluence |
docs/integrations/fallback-confluence.md |
github |
GitHub, GitHub Issues | Integration-GitHub |
docs/integrations/fallback-github.md |
gitlab |
GitLab | Integration-GitLab |
docs/integrations/fallback-gitlab.md |
azuredevops |
Azure DevOps, ADO, Azure Boards | Integration-AzureDevOps |
docs/integrations/fallback-azuredevops.md |
awscodecatalyst |
AWS CodeCatalyst, CodeCatalyst | Integration-AWSCodeCatalyst |
docs/integrations/fallback-awscodecatalyst.md |
googleclouddevops |
Google Cloud DevOps, GCP, Google Cloud | Integration-GoogleCloudDevOps |
docs/integrations/fallback-googleclouddevops.md |
If the request names something not in this table (e.g. Linear, Notion),
say so and stop rather than guessing a page that doesn't exist — offer to
add one (edit docs/integrations/README.md and register a new fallback
file the same way as the eleven above).
2. Try the live wiki page first
Build the URL from wiki.root_url in .work/config.yml (currently
https://github.com/SpillwaveSolutions/wiki_ticket_sdd/wiki) plus
/<Wiki page> from the table above. WebFetch it. The wiki copy is the
freshest source — per wiki-publish/SKILL.md, pages can be hand-edited
directly in the web UI, so it can be ahead of what's committed here.
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 7a153232b2e0
- 4d ago First seen · 97 lines · 99 tokens per session scan A 291e590ca00e
integration-guide is a skill published in the GitHub repository SpillwaveSolutions/wiki_ticket_sdd (10 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 1,418 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.
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…