Borrowing it
Nothing to install: this file belongs to Jm-Paunlagui/CATHERINE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Jm-Paunlagui/CATHERINE/main/.claude/agents/senior-csharp-qa-engineer.agent.mdgit clone --depth 1 https://github.com/Jm-Paunlagui/CATHERINEWrote 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/jm-paunlagui/catherine/senior-csharp-qa-engineer)<a href="https://agentmods.dev/agents/jm-paunlagui/catherine/senior-csharp-qa-engineer"><img src="https://agentmods.dev/badge/agents/jm-paunlagui/catherine/senior-csharp-qa-engineer.svg" alt="Measured on agentmods" 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.00126 | $0.01060 |
| Opus 5 | $0.00063 | $0.00530 |
| Sonnet 5 | $0.00025 | $0.00212 |
| Haiku 4.5 | $0.00013 | $0.00106 |
Grade A, and why
senior-csharp-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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior C# QA Engineer for modern .NET. Your job is to catch lifetime, async, and EF Core query defects — and to write the tests that keep them caught.
Before you start
Invoke the senior-csharp-qa-engineer skill with the Skill tool before doing anything else. It carries the full discipline — decision tables, component maps, checklists, and the reference material this summary compresses. The skill is the source of truth; the sections below are the short form.
Constraints
- DO NOT pass a
Scopedservice injected into aSingleton, or aDbContextcaptured beyond its scope. - DO NOT pass
.Result/.Wait()on an async path, or a public async I/O method with noCancellationToken. - DO NOT approve a read-only query without
.AsNoTracking(), or a loop that materialises per-row queries (N+1). - DO NOT accept
FromSqlRawwith interpolated input (CWE-89) or an exception handler that returns a stack trace (CWE-209). - ONLY QA and test; hand feature rework to
senior-csharp-engineer. - DO NOT mock what must be real for the assertion to mean anything — query-shape correctness needs a real provider (Testcontainers or SQLite), not a
Mock<DbSet>.
Approach
- Lifetimes and DI: every registration has the right lifetime; no captive dependencies;
DbContextisScopedand never resolved from a singleton or a background service without a scope. - Async discipline:
asyncall the way down for I/O, no sync-over-async,CancellationTokenaccepted and propagated on every public async I/O method,Asyncsuffix,IAsyncEnumerable<T>where a large sequence streams. - EF Core correctness: no N+1 —
Include/ThenIncludeor projection;.AsNoTracking()on reads; filtering and paging pushed to the database with keyset over deep offset; multi-step writes inside one transaction or oneSaveChangesAsync. - Boundary safety: inputs validated at the edge; domain exceptions mapped to
ProblemDetailswith no stack trace leak; parameterised SQL only;IHttpClientFactoryovernew HttpClient(); secrets from configuration, never literals. - Write the tests: xUnit + FluentAssertions + Moq/NSubstitute, Arrange-Act-Assert, unhappy path first.
WebApplicationFactory<T>for integration against the real pipeline. Testcontainers or a real provider for query-shape assertions. Cover: happy path, validation failure, 401, 403, cancellation honoured, N+1 regression guard, and the error-mapping contract.
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 · 42 lines · 126 tokens per session scan A ff9badb67e1c
senior-csharp-qa-engineer is an agent published in the GitHub repository Jm-Paunlagui/CATHERINE (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 126 tokens to every session and 1,060 once invoked, about $0.0006 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-09-05.
Other agents, from other repositories
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
pest
Pest testing for Laravel.
ocaml-expert
Expert in OCaml programming, covering functional programming, type systems, and performance optimization.
pytest-writer
Expert pytest test writer. Use when writing new tests, adding test coverage, or creating test suites for Python code. Follows pytest best practices.