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/cdsecurity/cdsecurity-skills/testing-agentgit clone --depth 1 https://github.com/CDSecurity/cdsecurity-skillsWhat 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.01215 |
| Opus 5 | $0.00000 | $0.00607 |
| Sonnet 5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00121 |
Grade A, and why
testing-agent 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Agent — Phases 1 & 2
Read your bundle for: framework, project_dir, test file list, in-scope source file list.
Phase 1: Test Coverage (15%)
Step 1: Run coverage
- Foundry:
forge coverage 2>&1(timeout 300s) - Hardhat:
npx hardhat coverage 2>&1(timeout 300s)
If successful, extract per-contract line and branch coverage percentages. Report each in-scope contract as a separate FAIL or PASS line with its coverage numbers. If it fails (missing deps, compile error, timeout), estimate from test file matching and note "estimated".
Step 2: Match test files to source
Compare in-scope source files against test files. A source contract has coverage if a test file exists that imports or references it.
Step 3: Compiler health
- Foundry:
forge build 2>&1 | grep -ci warning - Hardhat:
npx hardhat compile 2>&1 | grep -ci warning
Scoring
- Base score = average branch coverage % (or estimated coverage)
- If estimated: apply -10 confidence penalty
- Compiler warnings: -10 each (cap -30) — these MUST be fixed before audit
- Untested contracts (no matching test file): -15 each (cap -45)
Coverage threshold
After computing score, check: if branch coverage < 90%, emit this FAIL:
FAIL | below_threshold | -0 | n/a
desc: Branch coverage XX% — audit requires minimum 90%
fix: Add tests to reach 90%+ branch coverage before scheduling audit
This is informational (no extra deduction — the low base score already penalizes) but signals the project is NOT audit-ready.
Output:
Report each contract individually, then a total line:
PHASE 1 | Test Coverage | SCORE: 70/100
FAIL | below_threshold | -0 | n/a
desc: Branch coverage 70% — audit requires minimum 90%
fix: Add tests to reach 90%+ branch coverage before scheduling audit
FAIL | contract_coverage | -0 | src/core/Vault.sol
desc: Vault.sol — 45% line, 32% branch
fix: Add tests for deposit(), withdraw(), and edge cases
FAIL | no_coverage | -15 | src/libs/MathLib.sol
desc: No test file for MathLib (5 functions)
fix: Create test/MathLib.t.sol with unit tests
PASS | contract_coverage | src/core/Token.sol
note: Token.sol — 98% line, 95% branch
PASS | contract_coverage | src/core/Oracle.sol
note: Oracle.sol — 100% line, 100% branch
FAIL | compiler_warning | -10 | src/Token.sol:42
desc: Compiler warning: unused variable — must fix before audit
fix: Remove or use the declared variable
PASS | total_coverage
note: Overall: 70% line, 65% branch across 8 contracts
END PHASE 1
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 · 126 lines · 0 tokens per session scan A 7a313ebf5567
testing-agent is an agent published in the GitHub repository CDSecurity/cdsecurity-skills (50 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,215 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 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.