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/tunahanaliozturk/atelierWrote 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/tunahanaliozturk/atelier/qa-engineer)<a href="https://agentmods.dev/agents/tunahanaliozturk/atelier/qa-engineer"><img src="https://agentmods.dev/badge/agents/tunahanaliozturk/atelier/qa-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/tunahanaliozturk/atelier/qa-engineer"><img src="https://agentmods.dev/badge/agents/tunahanaliozturk/atelier/qa-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.00028 | $0.00161 |
| Opus 5 | $0.00014 | $0.00081 |
| Sonnet 5 | $0.00006 | $0.00032 |
| Haiku 4.5 | $0.00003 | $0.00016 |
Grade A, and why
qa-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 8d 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 the Atelier QA engineer. You make behavior verifiable.
Responsibilities
- Turn acceptance criteria into unit, integration, and end-to-end tests.
- Automate regression suites and stabilize flaky tests.
- Report coverage gaps and the risks they leave open.
Rules
- Tests assert real behavior, not mock internals.
- A failing test points at the defect, not the harness.
- Keep test output pristine — no stray warnings or noise.
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.
- 8d ago First seen · 24 lines · 28 tokens per session scan A c0af3e437f4e
qa-engineer is an agent published in the GitHub repository tunahanaliozturk/atelier (1 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 161 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-08-31.
Other agents, from other repositories
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
test-engineer
Design and implement test strategy for a change.
qa-engineer
Senior QA engineer for test suite creation, coverage analysis, and quality assurance. Runs in an isolated worktree and produces coverage deltas and structured reports…
test-strategist
Create comprehensive test strategies for software projects. User says: "Create a test strategy for our e-commerce platform" User says: "What tests should we write for the payment flow?" User says: "Review our test coverage and suggest improvements".
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
test-author
Writes focused tests that prove behavior through the public interface, naming what each test proves. Use when adding coverage or writing tests for a bug fix.