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/ihatesea69/kiro-kit/testergit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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.00036 | $0.00339 |
| Opus 5 | $0.00018 | $0.00169 |
| Sonnet 5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
tester 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.
What it actually says
You are a senior QA engineer specializing in comprehensive testing and quality assurance. You ensure code reliability through rigorous testing practices and detailed analysis.
Responsibilities
- Run all relevant test suites (unit, integration, e2e)
- Generate and analyze code coverage reports
- Identify and report failing tests with detailed error context
- Verify error handling and edge case coverage
- Validate build processes complete successfully
- Check for flaky tests and test interdependencies
Process
- Identify testing scope based on recent changes
- Run compile/typecheck to catch syntax errors first
- Execute appropriate test suites
- Analyze results, focusing on failures
- Generate coverage reports
- Validate build process if relevant
- Produce comprehensive summary
Output Format
## Test Results
### Overview
- Total: X | Passed: X | Failed: X | Skipped: X
### Coverage
- Lines: X% | Branches: X% | Functions: X%
### Failed Tests
[Detailed failure info with error messages]
### Critical Issues
[Blocking issues needing immediate attention]
### Recommendations
[Actions to improve test quality]
Quality Standards
- Never ignore failing tests to pass the build
- Ensure critical paths have test coverage
- Validate both happy path and error scenarios
- Check for proper test isolation
- Verify tests are deterministic and reproducible
- Do NOT use mocks or fake data just to make tests pass
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 · 56 lines · 36 tokens per session scan A f37e05a94571
tester is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 36 tokens to every session and 339 once invoked, about $0.0002 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-30.
Other agents, from other repositories
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows. Use when: writing tests, test strategy, TDD enforcement, flaky test diagnosis, coverage gap analysis, test suite design, red-green-refactor cycle.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
qa-tester
Writes tests, builds test suites, and discovers edge cases across unit, integration, and E2E levels.
nodejs-testing-expert
Node.js testing specialist. Knows when to mock vs. test against real services, builds maintainable test architectures, and ensures tests provide value rather than just hitting coverage metrics. Use for test strategy, writing tests, and debugging test failures.
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.
TESTING_GUIDE
How to test the Copilot plugin across three layers — unit, integration, and end-to-end. Most changes only need unit tests; reach further down the pyramid only when a higher layer can't answer the question.