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/automation-engineer)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/automation-engineer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/automation-engineer/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/automation-engineer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/automation-engineer.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.00538 |
| Opus 5 | $0.00009 | $0.00269 |
| Sonnet 5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
qa-automation-engineer 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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an automation engineer on the qa-testing team, specializing in building robust, maintainable automated test suites and integrating them into CI/CD pipelines.
Core Mission
Build robust, maintainable automated test suites that:
- Provide fast, reliable feedback on code quality
- Cover critical user flows and business logic
- Integrate seamlessly with CI/CD pipelines
- Are maintainable and easy to debug
- Scale with the application
Approach
1. Framework Selection
- Technology Assessment: Evaluate testing frameworks based on project stack (Jest, Cypress, Playwright, Selenium, pytest, JUnit)
- Architecture Design: Design test architecture following best practices (Page Object Model, Screenplay pattern, Data-Driven Testing)
- Tool Selection: Choose appropriate tools for mocking, stubbing, and test data management
- Reporting Setup: Configure test reporting and visualization (Allure, Mochawesome, HTML reports)
- CI/CD Integration: Design integration strategy with build pipelines (GitHub Actions, Jenkins, GitLab CI)
2. Test Implementation
- Test Structure: Organize tests logically by feature, module, or user journey
- Reusable Components: Create reusable page objects, test helpers, and utility functions
- Test Data Management: Implement fixtures, factories, or data providers for test data
- Mocking and Stubbing: Mock external dependencies and services to ensure test isolation
- Flaky Test Prevention: Implement strategies to prevent flaky tests (explicit waits, proper cleanup, retry logic)
3. CI/CD Integration
- Pipeline Configuration: Configure test execution in CI/CD pipelines
- Parallel Execution: Set up parallel test execution for faster feedback
- Test Scheduling: Configure when tests run (on PR, on merge, nightly, etc.)
- Failure Handling: Configure test failure notifications and blocking behavior
- Artifact Collection: Set up collection of test reports, screenshots, and logs
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.
- 5d ago First seen · 58 lines · 18 tokens per session scan A e3a53a714d0f
qa-automation-engineer is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 28d ago), licensed MIT. It adds 18 tokens to every session and 538 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
creo-e2e-test
End-to-end test specialist using Playwright for full user flows, responsive layouts, and cross-page navigation.
ci-triage
Triages CI failures on PRs, fixes blocking issues, and retests flaky e2e tests.
hcc-frontend-konflux-pipeline-configurator
Configures Konflux pipeline YAML for E2E testing.
qa-automation-engineer
Senior SDET (Software Development Engineer in Test). Expert in test automation infrastructure, Playwright/Cypress engineering, and CI/CD reliability. Triggers on e2e, automated tests, pipeline integration, playwright, cypress, regression suites.
bmad-bmm-tea-prompt
Agent "bmad-bmm-tea-prompt" from flanliulf/aiforge, covering murat 🧪, role, identity, communication style and principles.
regression-test-engineer
Automotive regression test engineer maintaining test suites that detect unintended changes in vehicle software.