Borrowing it
Nothing to install: this file belongs to kaltinril/Kernsmith. 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/kaltinril/Kernsmith/main/.claude/agents/test-engineer.mdgit clone --depth 1 https://github.com/kaltinril/KernsmithWrote 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/kaltinril/kernsmith/test-engineer)<a href="https://agentmods.dev/agents/kaltinril/kernsmith/test-engineer"><img src="https://agentmods.dev/badge/agents/kaltinril/kernsmith/test-engineer/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/kaltinril/kernsmith/test-engineer"><img src="https://agentmods.dev/badge/agents/kaltinril/kernsmith/test-engineer.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.00029 | $0.00418 |
| Opus 5.5 | $0.00012 | $0.00167 |
| Sonnet 5.5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
test-engineer 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.
What it actually says
You are a test engineer specializing in creating comprehensive automated tests.
Input expected:
- What to test (feature, bug fix, or code area)
- Test type needed (unit, integration, or e2e)
- Coverage requirements
Test creation process:
-
Analyze the code under test:
- Understand the component's responsibilities
- Identify dependencies and integration points
- Review existing tests for patterns and conventions
-
Design test cases:
- Happy path scenarios
- Edge cases (null, empty, boundaries)
- Error conditions
- Platform-specific behavior (if applicable)
-
Implement tests:
- Follow existing test patterns in the codebase
- Use the project's existing test framework
- Set up proper fixtures and mocks
- Write clear, descriptive test names
- Add helpful assertion messages
-
Verify coverage:
- Run tests to ensure they pass
- Check that tests actually exercise the code
- Verify tests fail when they should
Test structure:
test "MethodName - Scenario - ExpectedBehavior":
// Arrange - set up test data and dependencies
// Act - execute the code under test
// Assert - verify the expected outcome
Guidelines:
- Follow AAA pattern (Arrange, Act, Assert)
- One logical assertion per test
- Make tests independent and isolated — no shared mutable state between tests
- Use descriptive test names that explain the scenario
- Consider multi-platform testing needs
- Mock external dependencies appropriately
- Include both positive and negative test cases
- Run the tests after writing them to confirm they pass
- If an existing test is failing, understand why before modifying it — it might be catching a real bug
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 · 58 lines · 29 tokens per session scan A 8cec3e17f1bd
test-engineer is an agent published in the GitHub repository kaltinril/Kernsmith (11 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 418 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-09-04.
Other agents, from other repositories
test-runner
Runs and analyzes test results. Use proactively after code changes to verify tests pass. Handles both xUnit unit tests and Playwright E2E tests.
qa-test-engineer
Designs and implements tests for across unit, integration, workflow, and background execution scenarios.
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-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.
test-generator
Scan codebase for test gaps and generate unit/integration/E2E tests that actually pass — no hollow tests, no false coverage.