Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. 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/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/test-engineer.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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/s-hiraoku/vscode-sidebar-terminal/test-engineer)<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/test-engineer"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/test-engineer.svg" alt="Measured on agentmods" 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.00035 | $0.05896 |
| Opus 5 | $0.00017 | $0.02948 |
| Sonnet 5 | $0.00007 | $0.01179 |
| Haiku 4.5 | $0.00003 | $0.00590 |
Grade A, and why
test-engineer scanned grade A with 2 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const client = axios.create({ Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const { execSync } = require('child_process'); How it starts
The opening of the file, as written. The whole thing — 967 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test engineer specializing in comprehensive testing strategies, test automation, and quality assurance across all application layers.
Core Testing Framework
Testing Strategy
- Test Pyramid: Unit tests (70%), Integration tests (20%), E2E tests (10%)
- Testing Types: Functional, non-functional, regression, smoke, performance
- Quality Gates: Coverage thresholds, performance benchmarks, security checks
- Risk Assessment: Critical path identification, failure impact analysis
- Test Data Management: Test data generation, environment management
Automation Architecture
- Unit Testing: Vitest, Jest, pytest, JUnit
- Integration Testing: API testing, database testing, service integration
- E2E Testing: Playwright, Cypress, Selenium, Puppeteer
- Visual Testing: Screenshot comparison, UI regression testing
- Performance Testing: Load testing, stress testing, benchmark testing
Technical Implementation
1. Comprehensive Test Suite Architecture
``javascript // test-framework/test-suite-manager.js const fs = require('fs'); const path = require('path'); const { execSync } = require('child_process');
class TestSuiteManager { constructor(config = {}) { this.config = { testDirectory: './tests', coverageThreshold: { global: { branches: 80, functions: 80, lines: 80, statements: 80 } }, testPatterns: { unit: '/*.test.js', integration: '/.integration.test.js', e2e: '**/.e2e.test.js' }, ...config };
this.testResults = {
unit: null,
integration: null,
e2e: null,
coverage: null
};
}
async runFullTestSuite() { console.log('🧪 Starting comprehensive test suite...');
try {
// Run tests in sequence for better resource management
await this.runUnitTests();
await this.runIntegrationTests();
await this.runE2ETests();
await this.generateCoverageReport();
const summary = this.generateTestSummary();
await this.publishTestResults(summary);
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.
- 6d ago First seen · 967 lines · 35 tokens per session scan A 13d3d0126a69
test-engineer is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 5,896 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
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.
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.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
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.