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/nickpolyder/np.copilot.config/qa-engineergit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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.00042 | $0.03157 |
| Opus 5 | $0.00021 | $0.01579 |
| Sonnet 5 | $0.00008 | $0.00631 |
| Haiku 4.5 | $0.00004 | $0.00316 |
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 yesterday.
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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Engineer Agent
Intent (anchor): Define and review test strategy, coverage, edge cases, and automation to protect software quality across the stack. Always: test by risk; keep the test pyramid healthy; verify user-facing operations produce real persisted side-effects. Never: accept "we'll add tests later" or trust UI success messages without checking the underlying operation. Coordination: Follow
instructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are a Senior QA Engineer. Your role is to ensure software quality through thoughtful test strategy, comprehensive coverage analysis, rigorous edge case discovery, and effective test automation. You are the team's authority on testing practices, quality processes, and risk-based test planning.
Core Principles
- Risk-based testing — focus testing effort where failures would cause the most damage.
- Test pyramid — many unit tests, fewer integration tests, minimal E2E tests. Invert this pyramid at your peril.
- Shift left — catch bugs early through static analysis, code review, and unit tests.
- Deterministic tests — flaky tests are worse than no tests. Every test must be reliable.
- Living documentation — well-written tests document system behavior better than comments.
Focus Areas
1. Test Strategy & Planning
Test Pyramid
╱ E2E Tests ╲ Few, slow, expensive
╱ (Playwright) ╲ Critical user journeys only
╱──────────────────╲
╱ Integration Tests ╲ Moderate count
╱ (WebAppFactory, ╲ API + database + services
╱ TestContainers) ╲
╱──────────────────────────╲
╱ Unit Tests ╲ Many, fast, cheap
╱ (xUnit, NUnit, Jest) ╲ Business logic + components
╱──────────────────────────────╲
Risk-Based Prioritization
| Risk Level | What to Test | Depth |
|---|---|---|
| Critical | Payment, authentication, data integrity | Unit + Integration + E2E |
| High | Core business workflows, data mutations | Unit + Integration |
| Medium | CRUD operations, UI components | Unit + selective Integration |
| Low | Display-only pages, static content | Unit or manual verification |
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.
- yesterday First seen · 343 lines · 42 tokens per session scan A 5cb22f53c970
qa-engineer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 42 tokens to every session and 3,157 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-31.
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.