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/nickpolyder/np.copilot.config/test-gap-auditnpx skills add NickPolyder/NP.CoPilot.Config --skill test-gap-auditgit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWrote 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/nickpolyder/np.copilot.config/test-gap-audit)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/test-gap-audit"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/test-gap-audit.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.00039 | $0.01865 |
| Opus 5 | $0.00019 | $0.00932 |
| Sonnet 5 | $0.00008 | $0.00373 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
test-gap-audit 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Audit existing code and tests for risky coverage gaps, weak assertions, and missing edge cases without changing code. Always: scope the target; prioritize gaps by risk; present concrete test recommendations and stop at the generation hand-off. Never: write, edit, or delete tests or production code, or claim static analysis proves complete coverage.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor proportional work and verification.
The gap report is conversational by default. Persist it only when the user, repository policy, or a parent workflow explicitly requests a durable artifact; otherwise return the risk-prioritized findings without writing files.
You are conducting a read-only audit of existing code for dangerous untested paths.
Your goals are to:
- Find gaps — identify code paths, branches, and error scenarios that lack test coverage.
- Assess risk — prioritize gaps by the damage they can cause when they fail silently.
- Evaluate quality — flag existing tests that pass but don't actually verify meaningful behavior.
- Report next steps — produce a risk-prioritized gap report and recommend
test-gap-fillfor approved test generation.
When to use this skill
Use this skill whenever:
- A bug shipped that "should have been caught by tests" — retroactively identify the gap.
- Before a major refactoring — ensure the safety net exists before you lean on it.
- During maintenance cycles — periodic test health check.
- The user asks to "find untested code", "improve test coverage", or "audit tests for [module]".
- After a production incident — identify what tests would have prevented it.
- You need the first step in the chain:
test-gap-audit→ approval →test-gap-fill.
Do not use this skill for:
- Planning tests for new features — use
test-strategyinstead. - Running, debugging, generating, or editing tests — use
test-gap-fillafter approved gaps. - Code review — use
git-commit-revieworcode-revieweragent.
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.
- 4d ago First seen · 195 lines · 39 tokens per session scan A 7e61784570da
test-gap-audit is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 9d ago), licensed MIT. It adds 39 tokens to every session and 1,865 once invoked, about $0.0002 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…