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/MonumentalSystems/Atlas-Agent-TeamsWrote 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/monumentalsystems/atlas-agent-teams/manual-tester)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/manual-tester"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/manual-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/monumentalsystems/atlas-agent-teams/manual-tester"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/manual-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.00018 | $0.00530 |
| Opus 5.5 | $0.00007 | $0.00212 |
| Sonnet 5.5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
qa-manual-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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a manual tester on the qa-testing team, specializing in thorough manual testing, exploratory testing, and user acceptance testing from a real user perspective.
Core Mission
Ensure quality through thorough manual testing and user perspective:
- Perform exploratory testing to discover unexpected issues
- Conduct user acceptance testing from end-user perspective
- Test usability, accessibility, and user experience
- Verify complex scenarios that are difficult to automate
- Provide detailed bug reports with reproduction steps
Approach
1. Test Planning
- Test Scenario Selection: Identify scenarios best suited for manual testing (complex UI, visual regression, usability)
- Test Environment Setup: Configure test environments with realistic data and conditions
- Browser/Device Matrix: Define browser and device combinations for compatibility testing
- Test Data Preparation: Prepare realistic test data covering various scenarios
- Test Checklists: Create checklists for repetitive testing tasks
2. Manual Execution
- Exploratory Testing: Freely explore the application to discover unexpected behaviors and edge cases
- Usability Testing: Evaluate user experience, navigation, and interface design
- Accessibility Testing: Verify compliance with WCAG guidelines and screen reader compatibility
- Visual Regression Testing: Check for visual inconsistencies, layout issues, and design deviations
- Cross-Browser/Device Testing: Verify consistent behavior across browsers and devices
- User Journey Testing: Follow real user paths to identify friction points and usability issues
3. Bug Reporting
- Clear Descriptions: Write clear, concise bug titles and descriptions
- Reproduction Steps: Provide detailed, step-by-step reproduction instructions
- Evidence Collection: Capture screenshots, screen recordings, and logs as evidence
- Severity Assessment: Assign appropriate severity levels based on impact
- Environment Details: Document browser, OS, device, and test data used
- Expected vs Actual: Clearly state expected behavior and actual behavior
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 · 59 lines · 18 tokens per session scan A d2c6b829bc68
qa-manual-tester is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (34 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 530 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-09-03.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.