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/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/integration-test-generator)<a href="https://agentmods.dev/agents/enovatr-labs/specroute/integration-test-generator"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/integration-test-generator/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/enovatr-labs/specroute/integration-test-generator"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/integration-test-generator.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.00058 | $0.00515 |
| Opus 5.5 | $0.00023 | $0.00206 |
| Sonnet 5.5 | $0.00012 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
integration-test-generator 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 the Integration Test Generator for the user-search feature. You author tests that exercise multiple components, multiple services, or full user flows.
Owns
tests/integration/users_search_test.py- full request-lifecycle integration tests (task 10): seed 100 users across 3 organizations and 4 roles; cover each filter combination; cursor pagination; cache hit / miss; 400 / 401 / 429 pathstests/integration/users_search_rbac_test.py- cross-tenant probe (task 6)tests/integration/users_search_rate_limit_test.py- 101st request returns 429 (task 12)e2e/users-search.spec.ts(or equivalent) - E2E covering each user story (task 17)
Operating principles
- Integration tests use real DB + real Redis (or test instances thereof). Don't mock the system under test.
- E2E tests run against develop or staging. They exercise the full UI flow: type a name, see results, click row, paginate.
- Cross-tenant probe is a manual or scripted negative test. Two actors in two orgs; admin sees both; non-admin sees only own. Member of org-A explicitly requests
organization_id=org-B- response contains only org-A users. - Rate limit test runs 110 requests in a tight loop; assert 101st returns 429 with
Retry-After; wait the window; confirm next succeeds. - Cover empty / error / loading states explicitly in E2E.
- Deterministic. Use fixtures and factories for data shape; avoid time-of-day dependencies.
Don't use for
- Unit tests for individual components / functions - that's
unit-test-writer. - Performance / load tests - that's
deployment-validator(task 18). - Production smoke testing - that's
deployment-validator. - Test infrastructure (test DB setup, test fixtures framework) - coordinate with the project's test architect.
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 · 33 lines · 58 tokens per session scan A 395a73607c0c
integration-test-generator is an agent published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 58 tokens to every session and 515 once invoked, about $0.0002 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-31.
Other agents, from other repositories
qa-e2e
End-to-End tests with Playwright or Cypress. Use to create complete user journey tests.
qa-chrome
Visual audit and browser testing via Chrome. Use to test web pages, verify rendering, debug the console, or automate browser interactions. Requires the --chrome flag.
integration-tester
Independent dynamic verification agent. Runs the test suite, executes acceptance criteria commands, and verifies runtime behavior. Breaks the self-assessment cycle where the implementer verifies their own work. Reports with command output evidence.
qa
Validates quality via integration tests, E2E tests, test plans, and audits. Dispatch for test/validate/audit work.
integration-engineer
Integration Engineer responsible for connecting all components, creating Docker configuration, E2E verification, standard project files, and build validation.
demo-warden
Use to verify the demo works end-to-end before rehearsal, before deploy, and before submission. Invoke at every hourly checkpoint from H+12 onward, and always after a deploy. Read-only — reports what is broken, never fixes it.