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/noizefield/audio-plugin-coder/skill_troubleshootingnpx skills add Noizefield/audio-plugin-coder --skill skill_troubleshootinggit clone --depth 1 https://github.com/Noizefield/audio-plugin-coderWhat 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.00000 | $0.00415 |
| Opus 5 | $0.00000 | $0.00208 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
skill_troubleshooting 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 2d 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.
What it actually says
SKILL: TROUBLESHOOTING & ISSUE RESOLUTION
STEP 1: CHECK KNOWN ISSUES FIRST
Before trying random solutions: search ..agent/troubleshooting/known-issues.yaml.
WebView symptom shortcuts:
- Black screen → webview-007 / webview-010
- Messy / unstyled / overlapping HTML → webview-011 (
resolutions/webview-011-unstyled-external-css.md) - Knob dots, no arcs → webview-008
# Search known issues database
$errorPattern = "duplicate target juce"
$knownIssues = Get-Content ...agent\troubleshooting\known-issues.yaml | ConvertFrom-Yaml
$matches = $knownIssues.issues | Where-Object {
$_.error_patterns -match $errorPattern
}
if ($matches) {
Write-Host "✓ Known issue found: $($matches.title)"
Write-Host "Resolution: $($matches.resolution_file)"
# Load and apply solution
Get-Content "...agent\troubleshooting\$($matches.resolution_file)"
}
STEP 2: ATTEMPT RESOLUTION
[Your existing troubleshooting steps]
STEP 3: AUTO-CAPTURE NEW ISSUES
If after 3 attempts you haven't solved it:
# Create new issue entry
$newIssue = @{
id = "cmake-$(Get-Random -Max 999)"
title = "[Auto-generated from error]"
category = "build"
severity = "high"
symptoms = @($errorMessage)
resolution_status = "investigating"
}
# Append to known-issues.yaml
STEP 4: DOCUMENT SOLUTION
Once resolved:
# Update status to "solved"
# Fill out resolution document with:
# - What worked
# - Why it worked
# - How to prevent it
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.
- 2d ago First seen · 62 lines · 0 tokens per session scan A 8d42f77d002e
skill_troubleshooting is a skill published in the GitHub repository Noizefield/audio-plugin-coder (313 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 415 tokens. 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
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…