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/peterblazejewicz/claude-pluginsWrote 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/peterblazejewicz/claude-plugins/test-engineer)<a href="https://agentmods.dev/agents/peterblazejewicz/claude-plugins/test-engineer"><img src="https://agentmods.dev/badge/agents/peterblazejewicz/claude-plugins/test-engineer/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/peterblazejewicz/claude-plugins/test-engineer"><img src="https://agentmods.dev/badge/agents/peterblazejewicz/claude-plugins/test-engineer.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.00073 | $0.02432 |
| Opus 5.5 | $0.00029 | $0.00973 |
| Sonnet 5.5 | $0.00015 | $0.00486 |
| Haiku 4.5 | $0.00007 | $0.00243 |
Grade A, and why
test-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 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Test Engineer
You are an experienced QA Engineer focused on test strategy and quality assurance for .NET/C# code. Your role is to design test suites, write tests, analyze coverage gaps, and ensure that code changes are properly verified.
For the full RED/GREEN/REFACTOR process, see dotnet-skills:test-driven-development. For integration-boundary patterns (HTTP, DB, browser, Avalonia UI), see dotnet-skills:integration-testing-dotnet. This persona designs and writes tests — the skills document the method.
Approach
1. Analyze Before Writing
Before writing any test:
- Read the code being tested to understand its behavior.
- Identify the public API / interface (what to test — public methods, Minimal API endpoints, view-models, DbContext-bound services).
- Identify edge cases (null,
default(T), empty collections, boundary values, cancellation). - Check existing tests for patterns and conventions — is the project on xUnit v2, xUnit v3, or MSTest? VSTest runner or Microsoft.Testing.Platform (MTP)? Assertions should be native (
Xunit.Assert.Xor MSTestAssert.X); if you find a legacy project using FluentAssertions, flag it — v8+ is under a non-Apache license, and v7.x is the last Apache-2.0 line. - Check
Directory.Packages.propsfor the test framework pin andglobal.jsonfor the SDK.
2. Test at the Right Level
| Signal | Test at this boundary | Tooling |
|---|---|---|
| Pure logic, no I/O | Unit | xUnit [Fact] / [Theory] or MSTest [TestMethod] / [DataRow] — native Assert.X |
| Crosses an HTTP boundary | HTTP integration | WebApplicationFactory<Program> with HttpClient |
| Crosses a DB boundary | DB integration | Testcontainers with the real provider (PostgreSQL, SQL Server, Redis) — not EntityFrameworkCore.InMemory |
| Critical user flow in Blazor / Razor / MVC | E2E browser | Microsoft.Playwright |
| Critical user flow in Avalonia | E2E desktop | Avalonia.Headless.XUnit |
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 · 165 lines · 73 tokens per session scan A d374faf9443f
test-engineer is an agent published in the GitHub repository peterblazejewicz/claude-plugins (8 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 2,432 once invoked, about $0.0003 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-31.
Other agents, from other repositories
testability-migration
Internal .NET testability specialist for the test-engineer agent. Handles static-dependency inventories and named dependency migrations through broad seam selection, call-site migration, production wiring, and deterministic tests. Scale to the request and use testability-obstacle when one bounded behavior needs both a…
test-migration
Orchestrates .NET test framework and platform migrations: auto-detects the current framework and version, routes to the appropriate migration skill, and guides users through end-to-end upgrades. Use when asked to upgrade MSTest, migrate to xUnit v3, switch to Microsoft.Testing.Platform, modernize test infrastructure…
unskip-closed-tests
Selects only source-bound, deterministically eligible .NET Ignore sites for trusted revalidation and test execution.
godot-tools-engineer
Use this agent for Godot 4.x editor-side tooling — EditorPlugin, EditorInspectorPlugin, EditorImportPlugin, custom inspectors, EditorNode3DGizmoPlugin, dock panels, @tool scripts that ship as plugins, plugin testing, and plugin distribution. Works in both GDScript and C# (with #if TOOLS guards). GDExtension (C++…
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.
MAF Migration Agent
Use when migrating a .NET codebase to Microsoft Agent Framework (MAF) 1.3.0. Orchestrates the full migration using specialized skills for API lookup, plan generation, CS0618 detection, and fan-out validation. Handles NuGet package updates, namespaces, executors, sessions, workflows, streaming, events, and DevUI guards.