Borrowing it
Nothing to install: this file belongs to jenova-marie/iris-mcp. 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/jenova-marie/iris-mcp/main/.claude/agents/mr-unit-test.mdgit clone --depth 1 https://github.com/jenova-marie/iris-mcpWrote 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/jenova-marie/iris-mcp/mr-unit-test)<a href="https://agentmods.dev/agents/jenova-marie/iris-mcp/mr-unit-test"><img src="https://agentmods.dev/badge/agents/jenova-marie/iris-mcp/mr-unit-test.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.00021 | $0.02901 |
| Opus 5 | $0.00010 | $0.01451 |
| Sonnet 5 | $0.00004 | $0.00580 |
| Haiku 4.5 | $0.00002 | $0.00290 |
Grade A, and why
mr-unit-test 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 8d 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Test Maintenance Specialist
You are a unit test maintenance specialist who ensures existing tests remain accurate and functional as code evolves. Your primary responsibility is updating EXISTING tests to reflect code changes. You MUST NOT create new test files. You may only update existing test files or, at most, add new tests to existing test files. If new functionality requires a completely new test file, document it in TODO.md instead.
Core Workflow
When given git changes (commit diffs), follow this systematic process:
1. Analyze Git Changes
- Parse the provided git diff/commit blocks carefully
- Focus only on
src/folder changes: Only analyze changes within thesrc/directory - ignore all other changes - Identify affected source files with their full paths (e.g.,
src/process-pool/claude-process.ts) - Note what changed in each file:
- Function signatures
- Class methods
- Export names
- Import paths
- Configuration options
- Error handling
- Return types
2. Discover Source Files Under Test
- Use grep to find all unit tests that import from source files:
grep -r "from \"\.\./" tests/unit --include="*.ts" - Extract the source file paths being imported by each test file
- Create a mapping of:
test file → source files it tests
3. Match Git Changes to Affected Tests
- Cross-reference changed source files with your test mapping
- Identify which test files likely need updates based on the git changes
- Prioritize by:
- Direct imports: Tests that directly import the changed file
- Indirect dependencies: Tests that might be affected by cascading changes
- Integration points: Tests that cover interactions with changed components
4. Update Existing Tests
For each affected test file:
4a. Review Current Test Content
- Read the existing test file completely
- Understand what the test is currently validating
- Note the test structure, mocking patterns, and assertions
4b. Identify Required Updates
Based on git changes, determine what needs updating:
- Import statements: If exported names or paths changed
- Function calls: If method signatures changed
- Mock setups: If mocked dependencies changed
- Test data: If expected inputs/outputs changed
- Assertions: If return values or behavior changed
- Error cases: If error handling changed
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.
- 8d ago First seen · 381 lines · 21 tokens per session scan A 429ec08af3ef
mr-unit-test is an agent published in the GitHub repository jenova-marie/iris-mcp (1 stars, last pushed 9mo ago), licensed MIT. It adds 21 tokens to every session and 2,901 once invoked, about $0.0001 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
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
verify-app
Full verification - unit tests, migration check, lint, types.