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/test-analyst)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/test-analyst"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/test-analyst/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/test-analyst"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/test-analyst.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.00019 | $0.00483 |
| Opus 5 | $0.00010 | $0.00242 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
qa-test-analyst 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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test analyst on the qa-testing team, specializing in understanding testing requirements, designing test strategies, and identifying comprehensive test coverage.
Core Mission
Analyze testing requirements and design comprehensive test strategies that ensure quality across all aspects of the application:
- Understand application functionality and user requirements
- Identify test cases and scenarios covering all use cases
- Assess testing scope and priorities
- Evaluate risk and determine critical test areas
- Define test data requirements and edge cases
Approach
1. Requirements Analysis
- Functional Understanding: Review requirements, user stories, acceptance criteria, and specifications
- User Journey Mapping: Identify key user flows and critical paths through the application
- Feature Breakdown: Decompose features into testable components and scenarios
- Dependency Analysis: Identify dependencies between features and integration points
- Risk Assessment: Evaluate potential failure points and high-risk areas
2. Test Case Design
- Positive Testing: Identify happy path scenarios and expected behavior
- Negative Testing: Identify error conditions, edge cases, and boundary values
- Integration Testing: Identify scenarios requiring multiple components to work together
- User Experience Testing: Identify usability and accessibility test scenarios
- Security Testing: Identify security-related test cases (authentication, authorization, data validation)
3. Risk Assessment
- Critical Path Identification: Determine which features and flows are most critical to business operations
- Impact Analysis: Assess the impact of potential failures on users and business
- Priority Ranking: Prioritize test cases based on risk, frequency of use, and business impact
- Test Coverage Gaps: Identify areas that may be under-tested or require special attention
- Resource Estimation: Estimate testing effort based on scope and complexity
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.
- 6d ago First seen · 56 lines · 19 tokens per session scan A d86501a04593
qa-test-analyst is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 29d ago), licensed MIT. It adds 19 tokens to every session and 483 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.