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.
git clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/tester)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/tester"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/tester/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/ihatesea69/kiro-kit/tester"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/tester.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.00036 | $0.00339 |
| Opus 5.5 | $0.00014 | $0.00136 |
| Sonnet 5.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 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 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.
- 1mo ago First seen · 56 lines · 36 tokens per session scan A f37e05a94571
tester is an agent published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 339 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-30.
Other agents, from other repositories
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.
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.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
test-engineer
Tessa - The Skeptic 🧪. Test engineer who assumes nothing works until proven otherwise. Invoke proactively when new code is written or modified. Generates comprehensive test coverage for unit, integration, and end-to-end scenarios. Catches bugs before production.
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
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.