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 agents/csabakovacs/rulesmith/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.00003 | $0.00591 |
| Opus 5 | $0.00002 | $0.00296 |
| Sonnet 5 | $0.00001 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
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 — 62 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.
Trigger Conditions
- 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.
Methodology
- 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 convention:
<module>.test.tsmatching source module. (evidence: packages/core/test/dtree.test.ts, packages/core/test/fs.safe.test.ts) - Snapshot tests exist 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.
- Changes to
packages/core/src/render/should check for snapshot test impacts. (evidence: packages/core/test/snapshots/) - Changes to
packages/core/src/fs/safe.tsare high-risk — security boundary. (evidence: packages/core/test/fs.safe.test.ts)
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 · 62 lines · 3 tokens per session scan A 74f1cd06149e
test-guard is an agent published in the GitHub repository CsabaKovacs/rulesmith (15 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 591 once invoked, about $0.0000 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.