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/nishilbhave/codeprobe/codeprobe-testingnpx skills add nishilbhave/codeprobe --skill codeprobe-testinggit clone --depth 1 https://github.com/nishilbhave/codeprobeWhat 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.00075 | $0.01984 |
| Opus 5 | $0.00037 | $0.00992 |
| Sonnet 5 | $0.00015 | $0.00397 |
| Haiku 4.5 | $0.00007 | $0.00198 |
Grade A, and why
codeprobe-testing 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standalone Mode
If invoked directly (not via the orchestrator), you must first:
- Read
../codeprobe/shared-preamble.md(resolve relative to this SKILL.md's location — the siblingcodeprobeskill directory — not the user's project) for the output contract, execution modes, and constraints. - Load applicable reference files from
../codeprobe/references/(same resolution) based on the project's tech stack. - Default to
fullmode unless the user specifies otherwise.
Test Quality & Coverage Auditor
Domain Scope
This sub-skill detects test quality and coverage issues across six categories:
- Missing Tests — Public methods without corresponding tests, critical business logic untested.
- Test Smells — Tests with no assertions, testing implementation details, brittle tests.
- Test Structure — Missing Arrange-Act-Assert separation, poor naming, testing too many things.
- Mock Abuse — Mocking the system under test, mock returning mocks, over-mocking.
- Coverage Gaps — No tests for error paths, authorization logic, edge cases.
- Test Data — Hardcoded IDs, fragile fixtures, environment-dependent tests.
What It Does NOT Flag
- Missing tests for trivial getters/setters or pure DTOs — these add testing overhead without meaningful coverage.
- Framework-generated test stubs that are empty but clearly scaffolded (e.g., Laravel's
ExampleTest.php, Create React App'sApp.test.js) — these are starting points, not abandoned tests. - Integration/E2E test suites that intentionally don't follow unit test conventions — different test levels have different design constraints.
- Test execution speed — this sub-skill assesses test design quality, not runtime performance.
- Tests in
vendor/,node_modules/, or other dependency directories.
Detection Instructions
Severity Ceiling
No finding from this sub-skill should ever be classified as Critical. Missing tests, even for critical business logic, are a maintainability and risk issue (Major), not a confirmed production defect. The highest severity this sub-skill may assign is Major. Follow the severity column in each detection table exactly — do not escalate beyond 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 · 114 lines · 75 tokens per session scan A 96bc5383d38f
codeprobe-testing is a skill published in the GitHub repository nishilbhave/codeprobe (5 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 1,984 once invoked, about $0.0004 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.