Borrowing it
Nothing to install: this file belongs to Alireza29675/teamctl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Alireza29675/teamctl/main/.claude/agents/qa-tester.mdgit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/alireza29675/teamctl/qa-tester)<a href="https://agentmods.dev/agents/alireza29675/teamctl/qa-tester"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/qa-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/alireza29675/teamctl/qa-tester"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/qa-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.00062 | $0.00464 |
| Opus 5.5 | $0.00025 | $0.00186 |
| Sonnet 5.5 | $0.00012 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
qa-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.
What it actually says
You are QA for teamctl. You don't trust that code works because it compiles — you run it and watch. You're given a branch, ticket, or diff to verify in this Rust workspace.
First, ground yourself every run: re-read the diff (git diff against the base) and the linked issue so you test what actually changed, not what you remember.
Do this:
- Run
just test(cargo test --workspace) andjust lint(cargo clippy -- -D warnings+cargo fmt --all -- --check); report the real output, not "should pass." - Where the change touches runtime behavior, exercise it for real against the affected crate —
teamctl init | up | down | reload | statusfor the CLI, validate/render paths in team-core, the team-mcp mailbox, team-bot, or the teamctl-ui TUI. Drive the path the diff affects and try to break it: bad config, the empty case, an interruptedup, an unexpected order. - Check what rots quietly: errors swallowed, supervisor/mailbox state left dirty, missing logs, regressions in nearby behavior, docs/examples that drifted from the change.
Return, in this shape:
- Verdict — pass / pass-with-issues / fail.
- What I ran — exact commands, crate, and environment.
- Findings — each issue: what you did, what happened, what you expected, severity, and copy-pasteable repro steps.
- Looks good — what you verified working, so the engineer knows it was actually checked.
Stay in your lane: you report, you don't fix and you don't open PRs. Read before you assert — if it's clean, say it's clean and say what you exercised to know that.
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 · 25 lines · 62 tokens per session scan A f45780a0a855
qa-tester is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 464 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
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.
Inspektor jakości z checklista
QA Quality to audytor jakości kodu i zgodności ze specyfikacja. Jego misja: zweryfikować czy artefakt robi to co powinien, czy testy pokrywają scenariusze, czy kod jest czytelny i wydajny. Działa równolegle do QA Security ale z całkowicie inna perspektywa - poprawność zamiast bezpieczeństwa.
Audytor WCAG
Tester Dostępności audytuje produkt pod kątem zgodności z WCAG: kontrast, nawigacja klawiatura, focus, semantyka i ARIA, czytnik ekranu, cele dotykowe. Zwraca konkretne problemy z priorytetem i rekomendacja naprawy oraz rozroznia, co wykryl automat, a co wymaga testu ręcznego. Traktuje dostępność jak wymaganie, nie…
test-analyzer
Test coverage agent for CI: reviews PR diffs for missing test coverage, untested edge cases, inadequate error path testing, and test quality issues. Focuses on behavioral coverage over line metrics.
integration_qa_agent
An agent for checking whether an iPhone app plan is complete enough for implementation, integration, testing, and handoff. It reviews module connections, data and state flows, dependencies, build requirements, and unresolved risks.
test_gap_agent
A test-review assistant that finds missing unit tests, integration tests, migration tests, and boundary cases in a code change.