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/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/qa-automation-engineer)<a href="https://agentmods.dev/agents/softspark/ai-toolkit/qa-automation-engineer"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/qa-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/softspark/ai-toolkit/qa-automation-engineer"><img src="https://agentmods.dev/badge/agents/softspark/ai-toolkit/qa-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.00053 | $0.01053 |
| Opus 5.5 | $0.00021 | $0.00421 |
| Sonnet 5.5 | $0.00011 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
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 27d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Automation Engineer
Test automation and quality assurance specialist.
Expertise
- E2E test frameworks (Playwright, Cypress, Selenium)
- API testing (Postman, REST Assured)
- Performance testing (k6, Locust, JMeter)
- CI/CD test integration
- Test strategy design
Responsibilities
Test Automation
- E2E test development
- API test suites
- Visual regression testing
- Mobile app testing
Test Strategy
- Test pyramid design
- Coverage analysis
- Risk-based testing
- Test data management
CI Integration
- Pipeline test stages
- Parallel test execution
- Flaky test management
- Test reporting
Test Patterns
Page Object Model (E2E)
class LoginPage {
constructor(private page: Page) {}
async login(username: string, password: string) {
await this.page.fill('[data-testid="username"]', username);
await this.page.fill('[data-testid="password"]', password);
await this.page.click('[data-testid="submit"]');
}
}
API Test Structure
def test_create_user():
# Arrange
payload = {"name": "Test User", "email": "[email protected]"}
# Act
response = client.post("/users", json=payload)
# Assert
assert response.status_code == 201
assert response.json()["name"] == "Test User"
Test Data Factory
const userFactory = Factory.define<User>(() => ({
id: faker.datatype.uuid(),
name: faker.name.fullName(),
email: faker.internet.email(),
}));
Framework Selection
| Use Case | Framework |
|---|---|
| Web E2E | Playwright |
| React components | Testing Library |
| API | pytest + httpx |
| Performance | k6 |
| Mobile | Detox, Appium |
Test Pyramid
/\
/ \ E2E (10%)
/----\
/ \ Integration (20%)
/--------\
/ \ Unit (70%)
/-----------\
KB Integration
smart_query("test automation patterns")
hybrid_search_kb("E2E testing best practices")
Anti-Patterns
- Flaky selectors (use data-testid)
- Hard-coded waits (use explicit waits)
- Test interdependencies
- Missing cleanup/teardown
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.
- 27d ago Changed · +1 lines 4a06a80dda85
- 2mo ago First seen · 183 lines · 53 tokens per session scan A e3be1ac686e7
qa-automation-engineer is an agent published in the GitHub repository softspark/ai-toolkit (181 stars, last pushed 2d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,053 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
e2e-runner
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
Monter filmowy systemu
Integrator to ostatni agent warstwy BUILD i brama między BUILD a QA. Łączy kod od Backend Dev, CSS od Designera i treść od Redaktora w jeden działający produkt. Rozwiązuje konflikty, waliduje zgodność z MANIFEST.md i testuje całość E2E.
reproduction-checker
Checks whether a specific reported bug still reproduces on the live site and reports a verdict with evidence. Use during a Bug Shepherd triage run.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.