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/csabakovacs/rulesmith/test-guardnpx skills add CsabaKovacs/rulesmith --skill test-guardgit clone --depth 1 https://github.com/CsabaKovacs/rulesmithWhat 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.00031 | $0.00601 |
| Opus 5 | $0.00015 | $0.00300 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
test-guard 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Guard
Evaluates test coverage for recent changes, identifies missing tests, and flags regression risks.
When to Activate
- After ANY code modification that changes application logic, adds features, or modifies public interfaces.
- Skip for documentation-only, style-only, or config-only changes that do not affect runtime behavior.
Evaluation Methodology
Follow these steps in order:
- Identify all changed files and the nature of each change (new feature, bug fix, refactor, API change).
- For each changed module, check if corresponding test files exist in
packages/core/test/. (evidence: packages/core/test/) - Evaluate whether existing tests cover the changed code paths.
- Flag missing test coverage: new public functions without tests, changed branches without assertions.
- Assess regression risk: changes to safe.ts, render pipeline, or scanner are high-risk.
- Test command:
pnpm -r test(vitest). (evidence: package.json) - Test naming:
<module>.test.tsmatching source module. (evidence: packages/core/test/dtree.test.ts) - Snapshot tests for render output — flag if render changes may break snapshots. (evidence: packages/core/test/snapshots/)
- Classify findings as: missing (no test exists), incomplete (test exists but doesn't cover change), regression-risk (existing test may break).
- Report ONLY when gaps are found — produce no output if coverage is adequate.
Stack-Specific Test Rules
- Check for vitest test files matching changed modules. (evidence: packages/core/test/)
- Exported function signature changes require corresponding test updates.
- Render changes should check snapshot impacts. (evidence: packages/core/test/snapshots/)
safe.tschanges are high-risk security boundary. (evidence: packages/core/test/fs.safe.test.ts)
Test Command
pnpm -r test
Boundaries
- Do NOT write tests — only identify gaps and recommend what should be tested.
- Do NOT flag missing tests for trivial getters, configuration, or generated code.
- Do NOT require 100% coverage — focus on behavioral contracts and high-risk paths.
- Focus on the changed code, not pre-existing coverage gaps.
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 · 67 lines · 31 tokens per session scan A 0fc312e6c47c
test-guard is a skill published in the GitHub repository CsabaKovacs/rulesmith (15 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 601 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-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.
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.