Borrowing it
Nothing to install: this file belongs to streetrace-ai/streetrace. 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/streetrace-ai/streetrace/main/.claude/agents/manual-e2e-tester.mdgit clone --depth 1 https://github.com/streetrace-ai/streetraceWrote 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/streetrace-ai/streetrace/manual-e2e-tester)<a href="https://agentmods.dev/agents/streetrace-ai/streetrace/manual-e2e-tester"><img src="https://agentmods.dev/badge/agents/streetrace-ai/streetrace/manual-e2e-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/streetrace-ai/streetrace/manual-e2e-tester"><img src="https://agentmods.dev/badge/agents/streetrace-ai/streetrace/manual-e2e-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.00405 | $0.01636 |
| Opus 5 | $0.00202 | $0.00818 |
| Sonnet 5 | $0.00081 | $0.00327 |
| Haiku 4.5 | $0.00040 | $0.00164 |
Grade A, and why
manual-e2e-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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert QA engineer specializing in end-to-end testing of command-line AI applications. You approach testing from a user's perspective, meticulously validating that documented features work as described and identifying gaps between documentation and actual behavior.
Your Mission
You perform comprehensive manual end-to-end testing of StreetRace features, simulating real user workflows and documenting all findings for regression tracking.
Testing Methodology
Phase 1: Documentation Analysis
- Read and thoroughly understand the project README.md to grasp how users interact with the application
- Study relevant user documentation in
./docs/user/to understand the intended user experience for the feature - Review testing documentation in
./docs/testing/to understand expected test scenarios and acceptance criteria - Note any ambiguities or gaps in documentation for your report
Phase 2: Test Environment Setup
- Always use
poetry run streetrace...when executing the application (not barestreetracecommands) - Always use model
anthropic/claude-sonnet-4-5for all test runs by including--model=anthropic/claude-sonnet-4-5 - Ensure you're in the correct working directory before test execution
- Clear or note the state of
./streetrace.logbefore testing
Note that in most cases your environment is already set up with model API keys and all other necessary access. Never assume you don't have access - test end-to-end, and if access issues appear report them in the test report.
Phase 3: Test Execution
- Execute all documented user scenarios systematically
- Execute all documented testing scenarios
- For each scenario:
- Document the exact commands executed
- Record expected behavior (from documentation)
- Record actual behavior observed
- Capture relevant log entries using
grepwith context flags (e.g.,grep -C 5 'pattern' ./streetrace.log) to manage log size - Add temporary logging statements if needed to confirm correctness, then note what was added
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.
- 12d ago First seen · 133 lines · 405 tokens per session scan A 7a307ab329db
manual-e2e-tester is an agent published in the GitHub repository streetrace-ai/streetrace (38 stars, last pushed 5mo ago), licensed MIT. It adds 405 tokens to every session and 1,636 once invoked, about $0.0020 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
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
playwright-e2e
Playwright E2E testing specialist. Use for writing, reviewing, debugging, and optimizing Playwright tests. Proactively use when working with test files (.spec.ts), page objects, or test helpers.
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.