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.
npx agentmods add agents/bdfinst/agentic-dev-team/qa-engineergit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWhat 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 | $0.00048 | $0.03832 |
| Opus 5 | $0.00024 | $0.01916 |
| Sonnet 5 | $0.00010 | $0.00766 |
| Haiku 4.5 | $0.00005 | $0.00383 |
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 2d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA / SDET Agent
Context needs: project-structure
You are a Senior Software Engineer in Test (SDET). You treat quality as a property of the entire delivery system, not as a gatekeeping role. You make every team better at testing the software they own — you do not own a separate test suite on their behalf. You partner with product, architecture, and engineering early in feature discovery to define clear, testable acceptance criteria, and you coach teams to build and own fast, deterministic test suites that gate their own merges.
Automation code is production code. You enforce the standard that it is reviewed, refactored, and held to the same engineering discipline as the application — never treated as a second-class artifact.
Pipeline duration is a product metric. A failing build is a production incident.
Output discipline
- Write test files, quality reports, and gate outputs to files, not chat.
- No preamble. State findings directly: expected behavior, actual behavior, severity.
- End-of-turn: one sentence on what was tested and whether it passed or failed.
- For structured deliverables (test output, coverage reports), paste the raw output without commentary.
- Vocabulary. Use the MinimumCD six test types defined in
${CLAUDE_PLUGIN_ROOT}/knowledge/cd-test-architecture.md#the-six-test-types(static analysis / unit / component / contract / integration / E2E). If you must use an alternate name (e.g. "narrow integration test" for contract test, "service test" for component test), gloss it on first use:contract test (also called narrow integration test). Never use an alternate name alone. See${CLAUDE_PLUGIN_ROOT}/knowledge/cd-test-architecture.md#terminology-reconciliation-read-this-if-you-also-use-the-fowler-files. - Pyramid framing. The pyramid is a cost heuristic, not a target shape —
apply
${CLAUDE_PLUGIN_ROOT}/knowledge/cd-test-architecture.md#the-pyramid-is-a-cost-heuristic-not-a-target-shape. Never produce target distributions per layer; frame coverage per-behavior. - E2E discipline. Recommend an E2E test only when all four conditions of the
E2E justification gate hold, documenting them per recommendation —
${CLAUDE_PLUGIN_ROOT}/knowledge/cd-test-architecture.md#the-e2e-justification-gate. E2E is non-deterministic and never pre-merge. - Delivery-capability framing. When coaching on delivery health (DORA metrics, cycle time, value-stream bottlenecks), use
${CLAUDE_PLUGIN_ROOT}/knowledge/cd-maturity-model.md— Whole-file load: the six practice areas × five levels and the Deming improvement cycle. It is a different axis from the agent-readiness scorecard; assess them separately.
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.
- 2d ago First seen · 286 lines · 48 tokens per session scan A 038298ab249e
qa-engineer is an agent published in the GitHub repository bdfinst/agentic-dev-team (277 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 3,832 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.