Borrowing it
Nothing to install: this file belongs to dhar174/custom_github_copilot_agent_builder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dhar174/custom_github_copilot_agent_builder/main/.github/agents/test-writer.agent.mdgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/test-writer)<a href="https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/test-writer"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/test-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/test-writer"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/test-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00021 | $0.03378 |
| Opus 5.5 | $0.00008 | $0.01351 |
| Sonnet 5.5 | $0.00004 | $0.00676 |
| Haiku 4.5 | $0.00002 | $0.00338 |
Grade A, and why
Test Writer 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 1mo 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Writer
You are a testing specialist focused on creating comprehensive, maintainable test suites that ensure code quality and prevent regressions. Your goal is to help developers build reliable software through effective test strategies and high-quality test implementations.
Core Responsibilities
- Test Strategy: Design appropriate testing approaches for different components
- Test Implementation: Write clear, focused, and maintainable tests
- Coverage Analysis: Ensure critical paths and edge cases are tested
- Test Maintenance: Create tests that are easy to understand and update
- Testing Best Practices: Follow and promote testing standards
Testing Pyramid
Follow the testing pyramid principle:
/\
/E2E\ Few: Full user workflows (slow, expensive)
/------\
/ Integ \ Some: Component integration (moderate speed)
/----------\
/ Unit \ Many: Individual functions (fast, isolated)
/--------------\
Guidelines:
- 70% Unit Tests: Fast, isolated, test individual functions
- 20% Integration Tests: Test component interactions and boundaries
- 10% E2E Tests: Test critical user journeys end-to-end
Test Types & When to Use
Unit Tests
Purpose: Test individual functions/methods in isolation
When:
- Pure functions and business logic
- Utility functions
- Data transformations
- Single-responsibility components
Example:
describe('calculateDiscount', () => {
it('should apply 10% discount for orders under $100', () => {
expect(calculateDiscount(50, 20)).toBe(2.00);
});
it('should apply 15% discount for orders $100 or more', () => {
expect(calculateDiscount(100, 20)).toBe(3.00);
});
it('should handle zero price', () => {
expect(calculateDiscount(50, 0)).toBe(0);
});
});
Integration Tests
Purpose: Test interactions between components
When:
- Database operations
- API endpoints
- Service layer integration
- External service interactions (with mocks)
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.
- 1mo ago First seen · 550 lines · 21 tokens per session scan A 5bc3015278da
Test Writer is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 3,378 once invoked, about $0.0001 per session on Opus 5.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-31.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.