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/dhar174/custom_github_copilot_agent_builder/test-writergit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWhat 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.00021 | $0.03378 |
| Opus 5 | $0.00010 | $0.01689 |
| Sonnet 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 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 — 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.
- 2d 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 7mo ago), licensed MIT. It adds 21 tokens to every session and 3,378 once invoked, about $0.0001 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-31.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.