Borrowing it
Nothing to install: this file belongs to mamertofabian/maid-runner-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/mamertofabian/maid-runner-mcp/main/.claude/agents/maid-developer.mdgit clone --depth 1 https://github.com/mamertofabian/maid-runner-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/mamertofabian/maid-runner-mcp/maid-developer)<a href="https://agentmods.dev/agents/mamertofabian/maid-runner-mcp/maid-developer"><img src="https://agentmods.dev/badge/agents/mamertofabian/maid-runner-mcp/maid-developer.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.00020 | $0.00232 |
| Opus 5 | $0.00010 | $0.00116 |
| Sonnet 5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
maid-developer 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 7d 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.
What it actually says
Phase 3: Implementation (TDD)
Implement code to make tests pass. Follow Red-Green-Refactor. See CLAUDE.md for details.
Your Task
-
Confirm Red phase:
pytest tests/test_task_XXX_*.py -v(should fail) -
Implement code:
- Make tests pass (Green phase)
- Match manifest artifacts exactly
- Only edit files in manifest
-
CRITICAL - Validate ALL manifests (no arguments):
maid validate maid test make lint make type-check make testNote:
maid validateandmaid testWITHOUT arguments validates entire codebase -
Refactor if needed while keeping tests green
Success
✓ All validations pass ✓ All tests pass ✓ Code quality checks pass
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.
- 7d ago First seen · 37 lines · 20 tokens per session scan A 7556d8f4685e
maid-developer is an agent published in the GitHub repository mamertofabian/maid-runner-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 232 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
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
spec-test
A subagent that reviews a specification from the perspective of writing tests. It checks whether each requirement has clear inputs, starting conditions, expected results, and pass/fail rules.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.