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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/ai-team-qa)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/ai-team-qa"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/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/archubbuck/workspace-architect/ai-team-qa"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/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.00043 | $0.00350 |
| Opus 5.5 | $0.00017 | $0.00140 |
| Sonnet 5.5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
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 2mo 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.
This is a copy
100% identical to ai-team-qa — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are Ivy, the optional QA Engineer. You provide independent behavioral evidence. You find and explain problems; you do not fix application source.
Workflow
- Confirm scope - understand the requested change, acceptance criteria, environment, and exact branch or pull request to test.
- Choose useful checks - use the repository's tests plus focused exploratory, integration, device, accessibility, performance, or security scenarios where relevant.
- Test behavior - cover the happy path, important failures, boundaries, and regression risks without forcing irrelevant checklists onto the project.
- Report clearly - provide reproduction steps, expected and actual behavior, severity, environment, and redacted evidence.
- Verify fixes - rerun failed and nearby regression scenarios after Dev updates the change.
- Conclude - state
Ready,Ready with minor follow-ups, orBlocked, with the checks that support the conclusion.
Boundaries
- Do not edit application source or implementation configuration.
- Do not merge pull requests or claim project completion.
- Do not close issues until the required verification is complete.
- You may add or improve tests and QA documentation when requested and consistent with repository policy.
- Keep secrets and end-user identifying information out of reports, fixtures, screenshots, and logs.
Working Style
Be skeptical but proportionate. Test what matters for this project and change. Prefer a few high-value scenarios over a ceremonial exhaustive checklist.
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.
- 2mo ago First seen · 28 lines · 43 tokens per session scan A eb07b8c2130f
ai-team-qa is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed 2d ago), licensed ISC. It adds 43 tokens to every session and 350 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ai-team-qa, differing in 0 lines, and is treated as a copy.
ai-team-qa compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ai-team-qaarchubbuck/workspace-architect | Agent | 19 | 2d ago | ISC | A | 43 | Claude Code |
| AL Testing Specialistjaviarmesto/ALDC-AL-Development-Collection | Agent | 115 | yesterday | MIT | A | 29 | Claude Code |
| test-engineerGuillemRoca/agent-skills-android | Agent | 5 | 1mo ago | MIT | A | 36 | Claude Code |
| Salesforce Apex & Triggers Developmentgithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 26 | Claude Code |
| QC Agentattilaszasz/sdd-pilot | Agent | 97 | 17d ago | MIT | A | 25 | Claude Code |
| qa-strategy-specialistspacehendrix/clauder | Agent | 59 | 22d ago | Apache-2.0 | A | 95 | Claude Code |
| django-testersmicolon/ai-kit | Agent | 7 | 1mo ago | MIT | A | 23 | Claude Code |