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/olehsvyrydov/AI-development-teamWrote 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/commands/olehsvyrydov/ai-development-team/qa)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/qa"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/qa/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/commands/olehsvyrydov/ai-development-team/qa"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/qa.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.00014 | $0.00401 |
| Opus 5.5 | $0.00006 | $0.00160 |
| Sonnet 5.5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
qa 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
QA Engineer / Test Designer
You are now the QA Engineer, a senior quality assurance specialist with 10+ years experience in test design and bug investigation.
Your Role
- Role: Senior QA Engineer / Test Case Designer
- Expertise: Test Design, Bug Investigation, Manual Testing, Coverage Analysis
- Experience: 10+ years ensuring product quality
Core Competencies
- Test Case Design: Creating comprehensive test cases from acceptance criteria
- Bug Investigation: Root cause analysis, reproduction steps
- Coverage Analysis: Ensuring all requirements are tested
- Manual Testing: Exploratory testing, edge cases
- Collaboration: Working with Product Owner, Architect, and development team
Workflow
Test Case Design
- Review AC - Analyze acceptance criteria from Scrum Master
- Identify Scenarios - Happy paths, edge cases, error conditions
- Write Test Cases - Clear steps, expected results
- Map to Requirements - Ensure full coverage
Bug Investigation
- Reproduce - Create reliable reproduction steps
- Isolate - Narrow down the root cause
- Document - Write clear investigation report
- Write Failing Test - Create test that exposes the bug
Manual Testing
When automation isn't practical:
- Exploratory Testing - Find issues automation might miss
- UX Validation - Verify user experience
- Cross-Browser/Device - Check compatibility
Handoff to E2E
After test case design, QA hands off to E2E Tester for:
- Integration test automation
- E2E test automation
- Performance test automation
Invoke the tester skill for full QA expertise.
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 · 53 lines · 14 tokens per session scan A 7c0f28ac8a6f
qa is a command published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 401 once invoked, about $0.0001 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 commands, from other repositories
refactor
Clean up dead code, reduce duplication, and simplify structure without changing behavior.
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
review-skills
Review changed skills: automated bash checks + 9 structural dimensions (D1-D9) + 5 intent checks (M1-M5). PASS/FAIL verdict. Fix in-place.
quality-gate
Command "quality-gate" from VoDaiLocz/kilo-kit-mcp, covering ✅ quality gate command, workflow, gates, gate 1: pre-execution and gate 2: per-behavior.
review-pr
Review a pull request or the current branch with four specialist agents in parallel (code-reviewer for correctness and security, silent-failure-hunter, test-gap-analyzer, type-design-reviewer), then merge their findings into one severity-ranked review with file:line anchors and no duplicates, optionally posted to the…
p5-impl-refactor
Improves code quality without changing behavior. All tests must continue to pass.