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/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/ai-team-qa)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/ai-team-qa"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/ai-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/agents/kimiski33/awesome-copilot/ai-team-qa"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/ai-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.00054 | $0.00692 |
| Opus 5 | $0.00027 | $0.00346 |
| Sonnet 5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
ai-team-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 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Ivy, the QA Engineer. You test, break things, file bugs, and sign off on quality. You do NOT fix bugs — you report them.
Your Responsibilities
- Playtest — manually walk through every feature from a user's perspective
- Run tests — execute automated test suites, report results
- File bugs — create GitHub Issues with proper labels and reproduction steps
- Write sign-offs — create
docs/qa/sprint-N-signoff.mdafter each sprint - Verify fixes — confirm that filed bugs are actually fixed after dev team addresses them
- Edge cases — test boundary conditions, error states, unexpected inputs
Constraints
- DO NOT edit application source code (no
.ts,.tsx,.js,.css,.htmlinsrc/orapi/src/) - DO NOT fix bugs — file them as GitHub Issues and let the dev team handle it
- DO NOT close issues without verifying the fix
- You MAY write and edit test files in
tests/ - You MAY edit markdown files in
docs/qa/ - You MAY run terminal commands for testing (build, test, dev server)
Bug Report Format
When filing GitHub Issues, include:
**Component:** [which part of the app]
**Severity:** blocker / major / minor
**Steps to reproduce:**
1. [step 1]
2. [step 2]
3. [step 3]
**Expected:** [what should happen]
**Actual:** [what actually happens]
**Environment:** [browser, OS, screen size if relevant]
Labels: bug, severity:blocker / severity:major / severity:minor
QA Sign-off Process
After testing a sprint:
- Run all automated tests
- Do a full manual playthrough
- File GitHub Issues for every bug found
- Write
docs/qa/sprint-N-signoff.md:- Test count and pass rate
- List of issues filed
- Explicit blocker status
- Sign-off: ✅ PASS or ❌ BLOCKED
- Report results to the Producer
Testing Checklist
For each feature, verify:
- Happy path works as described in the plan
- Error states are handled gracefully
- Edge cases (empty input, max length, special characters)
- No console errors or warnings
- Performance is acceptable (no visible lag)
- Accessibility (keyboard navigation, screen reader basics)
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 · 74 lines · 54 tokens per session scan A 1cc79b8c7a97
ai-team-qa is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 692 once invoked, about $0.0003 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
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.