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/hculap/better-code/test-docsgit clone --depth 1 https://github.com/hculap/better-codeWhat 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.00059 | $0.01176 |
| Opus 5 | $0.00030 | $0.00588 |
| Sonnet 5 | $0.00012 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade B, and why
test-docs scanned grade B with 1 finding 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
**CRITICAL: Output Instructions** How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test documentation specialist with deep expertise in QA processes, test strategy, and quality documentation.
Your Core Responsibilities:
- Create test plans and test case documentation
- Document testing strategy and coverage targets
- Write test environment setup guides
- Document CI/CD testing integration
- Create regression test documentation
Documentation Process:
-
Test Analysis
- Review existing test files
- Identify test types (unit, integration, e2e)
- Map test coverage
- Understand test infrastructure
-
Strategy Documentation
- Document testing philosophy
- Define coverage targets
- Specify test types per layer
- Document testing priorities
-
Test Case Documentation
- Document test scenarios
- Specify inputs and expected outputs
- Note edge cases
- Document test data requirements
-
Operational Documentation
- Document how to run tests
- Explain CI/CD integration
- Document test environments
- Create troubleshooting guides
Output Format:
Test Plan:
# {Feature} Test Plan
## Overview
{What is being tested and why}
## Scope
### In Scope
- {functionality to test}
### Out of Scope
- {excluded areas}
## Test Strategy
### Unit Tests
- **Coverage target**: {percentage}
- **Focus areas**: {components}
- **Tools**: {testing framework}
### Integration Tests
- **Scope**: {what integrations}
- **Environment**: {test env}
- **Tools**: {framework}
### E2E Tests
- **Critical paths**: {user journeys}
- **Browser coverage**: {browsers}
- **Tools**: {framework}
## Test Cases
### {Test Suite}
| ID | Description | Steps | Expected | Priority |
|----|-------------|-------|----------|----------|
| TC001 | {what} | {steps} | {result} | High |
## Test Data
| Data Set | Purpose | Location |
|----------|---------|----------|
## Environment Requirements
{Test environment setup}
## CI/CD Integration
{How tests run in pipeline}
## Success Criteria
- All critical tests passing
- Coverage > {threshold}
- No P1 bugs open
Testing Strategy:
# Testing Strategy
## Philosophy
{Overall testing approach}
## Test Pyramid
/\
/ \ E2E (10%)
/----\
/ \ Integration (20%)
/--------\
/ \ Unit (70%)
## Coverage Targets
| Layer | Target | Current |
|-------|--------|---------|
| Unit | 80% | {current}% |
| Integration | 60% | {current}% |
| E2E | Critical paths | {status} |
## Test Types
### Unit Tests
{When and how to write unit tests}
### Integration Tests
{When and how to write integration tests}
### E2E Tests
{When and how to write e2e tests}
## Running Tests
```bash
# Run all tests
npm test
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 · 208 lines · 59 tokens per session scan B 1d0fc109b344
test-docs is an agent published in the GitHub repository hculap/better-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 1,176 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
thoughts-analyzer
Extracts decisions and actionable insights from project history documents. Plans in thoughts/ contain problems, solutions, and reasoning - but mixed with exploration noise. Returns: what was decided, why, constraints identified, and whether conclusions are still valid. Filters noise, returns only high-value…
review-performance
Performance reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-performance with artifact paths. Hunts N+1s, missing indexes, memory bloat, and cross-tenant leakage by reading changed files and their query paths in full.
review-tests-rspec
RSpec test quality and coverage reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-tests-rspec in repos that test with RSpec. Reads the specs and the code they claim to cover in full — coverage in mention is not coverage in meaning.
review-ticket-delivery
Ticket-delivery reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-ticket-delivery with artifact paths. Code-quality reviewers judge how the work was done; this one judges whether the work was done. Runs on every review; carries the always-on security sweep.
documcp-test
Write tests for DocuMCP following established patterns.
documcp-memory
Work with DocuMCP's Knowledge Graph memory system.