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/continuedev/continue/test-coveragegit clone --depth 1 https://github.com/continuedev/continueWhat 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.00009 | $0.00494 |
| Opus 5 | $0.00005 | $0.00247 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
Test Coverage 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Check
Review this pull request to determine if new functionality has adequate test coverage.
When Tests Are Expected
-
New exported functions or classes - Any new public function, class, or module that is exported and used by other parts of the codebase should have at least basic unit tests covering:
- The happy path (expected inputs produce expected outputs)
- Edge cases (empty inputs, null/undefined, boundary values)
- Error cases (invalid inputs throw or return appropriate errors)
-
New CLI commands or subcommands - Should have:
- Smoke tests verifying the command registers and runs
- Tests for flag parsing and validation
- Tests for expected output format
-
Bug fixes - If a PR fixes a bug, there should be a regression test that:
- Reproduces the original bug condition
- Verifies the fix resolves it
-
New API endpoints or handlers - Should have integration tests covering:
- Successful request/response
- Error responses for invalid inputs
- Authentication/authorization (if applicable)
When Tests Are NOT Expected
- Documentation-only changes
- Configuration file changes (YAML, JSON, Markdown)
- CSS/styling changes
- Dependency updates (unless they change behavior)
- Agent definition files (
.continue/agents/*.md) - Refactors that don't change behavior (existing tests should still pass)
- Internal implementation changes fully covered by existing tests
What to Do
- If new functionality lacks tests, add a PR comment noting what should be tested and why.
- Do NOT write tests yourself. The author knows the intended behavior best.
- If the PR includes tests but they seem incomplete (missing edge cases, no error cases), note the gaps.
- If the PR is clearly a test-exempt category (docs, config, styling), do nothing.
Test Infrastructure Reference
- Core: Jest (
*.test.ts) + Vitest (*.vitest.ts) incore/ - GUI: Vitest (
*.test.ts) ingui/src/ - CLI: Vitest (
*.test.ts,*.e2e.test.ts) inextensions/cli/ - Packages: Vitest in each
packages/*/directory
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.
- yesterday First seen · 57 lines · 9 tokens per session scan A d48f3f72b243
Test Coverage is an agent published in the GitHub repository continuedev/continue (35,702 stars, last pushed 2d ago), licensed Apache-2.0. It adds 9 tokens to every session and 494 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
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
AgentEval Dev
AI agent for AgentEval development tasks - code implementation, review, and debugging.