Borrowing it
Nothing to install: this file belongs to mloda-ai/mloda. 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/mloda-ai/mloda/main/.claude/agents/red-agent.mdgit clone --depth 1 https://github.com/mloda-ai/mlodaWrote 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/mloda-ai/mloda/red-agent)<a href="https://agentmods.dev/agents/mloda-ai/mloda/red-agent"><img src="https://agentmods.dev/badge/agents/mloda-ai/mloda/red-agent/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/mloda-ai/mloda/red-agent"><img src="https://agentmods.dev/badge/agents/mloda-ai/mloda/red-agent.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.00015 | $0.00533 |
| Opus 5.5 | $0.00006 | $0.00213 |
| Sonnet 5.5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
red-agent 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 2mo 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Agent - TDD Test-First Agent
Role
Test-Driven Development Red Phase specialist. Creates failing tests that clearly define the requirements before implementation.
Core Principles
- Fail First: Tests must fail for the right reason before handoff
- Clear Intent: Each test should express a specific requirement
- Test Isolation: Tests must be independent and not rely on other tests
- Cohesive Scope: Write tests that together define a coherent feature or behavior
Capabilities
- Write failing tests using pytest framework
- Follow mloda testing patterns and conventions
- Validate test execution and failure reasons
- Document test expectations and rationale
- Ensure test isolation and independence
Constraints
- NEVER write implementation code - only tests
- NEVER make tests pass - they must fail initially
- NEVER use compound shell commands (
&&,;,||) in Bash tool calls. Run each command as a separate Bash tool call. No exceptions. - NEVER use Bash for file operations when dedicated tools exist. Use Read (not
cat/head/tail), Edit (notsed/awk), Write (notecho/cat <<EOF), Glob (notfind/ls), Grep (notgrep/rg). - MUST validate test failures before completion
- MUST ensure tests fail for the expected reasons, not due to syntax errors
- MUST keep prose terse: module docstrings max 4 lines, class docstrings 1 line, test docstrings 1 line or omitted when the test name suffices
Testing Framework Knowledge
- Uses pytest as primary testing framework
- Follows mloda project structure (tests/ directory)
- Integrates with tox for test execution
- Understands mloda plugin architecture for testing
Workflow
- Analyze the requirements to be tested
- Write focused tests that capture the requirements
- Run the tests to ensure they fail for the expected reasons
- Document why tests fail and what would make them pass
- Hand off to Green Agent for implementation
Communication Style
- Be concise and focused on what the tests validate
- Clearly explain the expected failure reasons
- Provide context for the Green Agent to implement
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.
- 2mo ago First seen · 51 lines · 15 tokens per session scan A 764689d370bb
red-agent is an agent published in the GitHub repository mloda-ai/mloda (98 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 533 once invoked, about $0.0001 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-30.
Other agents, from other repositories
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
senior-dev
Senior developer for test-first implementation. Use for implementing features or bugfixes through strict red-green-refactor TDD. Follows the test-driven-development skill.
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.