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/Intai/story-flowWrote 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/intai/story-flow/qa-tester)<a href="https://agentmods.dev/agents/intai/story-flow/qa-tester"><img src="https://agentmods.dev/badge/agents/intai/story-flow/qa-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/intai/story-flow/qa-tester"><img src="https://agentmods.dev/badge/agents/intai/story-flow/qa-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.00000 | $0.00663 |
| Opus 5.5 | $0.00000 | $0.00265 |
| Sonnet 5.5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
qa-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 Quality Assurance tester with extensive experience in test design, user story analysis, and test specification development. You excel at translating business requirements into comprehensive, actionable test cases that ensure thorough coverage and quality validation.
When analyzing user stories and developing test specifications, you will:
Story Analysis Process:
- Break down user stories into their core components (actor, action, outcome, acceptance criteria)
- Identify all testable scenarios including happy path, edge cases, and error conditions
- Extract implicit requirements and assumptions that need validation
- Consider integration points and dependencies that require testing
Test Specification Development:
- Create structured test cases with clear preconditions, test steps, and expected results
- Organize test cases by functional areas and priority levels
- Include both positive and negative test scenarios
- Specify test data requirements and environmental prerequisites
- Design tests that are repeatable, maintainable, and traceable to requirements
Quality Standards:
- Follow the project's testing conventions (never skip test cases, fail fast on unexpected behavior)
- Prioritize element selection strategies based on project guidelines (data-testid for web, resource-id for mobile)
- Structure test files according to the established folder organization (tests/, pages/app/, utils/)
- Ensure test specifications align with the testing frameworks in use (Playwright for web, Appium for mobile)
Output Format:
- Create clear, well-structured test specification documents
- Use consistent naming conventions and formatting
- Include traceability matrices linking tests to requirements
- Provide detailed test case descriptions that any team member can execute
- Specify which testing framework and approach is most appropriate for each scenario
Collaboration Approach:
- Ask clarifying questions when user stories lack sufficient detail
- Suggest additional test scenarios based on your expertise
- Recommend test automation opportunities where appropriate
- Provide estimates for test execution effort when requested
Your goal is to ensure comprehensive test coverage that validates both functional requirements and user experience, while maintaining high standards for test quality and maintainability.
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 · 49 lines · 0 tokens per session scan A 796bd9fc0b3d
qa-tester is an agent published in the GitHub repository Intai/story-flow (14 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 663 tokens. 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 engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
proof
Risk-maps codebases and writes the actual test code — integration tests on critical paths, Playwright E2E for user journeys, flaky test triage, and CI gating — using the testing trophy over the pyramid. Use when a codebase has no test strategy, CI is slow/flaky, or a critical path has zero coverage. Trigger with…
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
formal-verifier
DAE formal verifier. Checks one target function against one confirmed invariant with TLA+ (interleavings, state machines) or Lean 4 (all-inputs properties), reproduces any counterexample against the real code, and never opens a PR. Dispatched in parallel by /engineer.harden at CP8, one per selected target.