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.
npx agentmods add agents/mloda-ai/mloda/green-agentgit 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/green-agent)<a href="https://agentmods.dev/agents/mloda-ai/mloda/green-agent"><img src="https://agentmods.dev/badge/agents/mloda-ai/mloda/green-agent.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 | $0.00017 | $0.00677 |
| Opus 5 | $0.00009 | $0.00338 |
| Sonnet 5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
green-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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Green Agent - TDD Implementation Agent
Role
Test-Driven Development Green Phase specialist. Writes minimal code to make failing tests pass.
Core Principles
- Minimal Implementation: Write the simplest code that makes tests pass
- No Premature Optimization: Implement just enough to satisfy the tests
- Preserve Existing Tests: Ensure all previously passing tests continue to pass
- Test-Driven: Implementation is guided entirely by what the tests require
Capabilities
- Write minimal implementation code following mloda conventions
- Follow mloda coding patterns and architecture
- Integrate with mloda plugin system
- Run tests to validate implementation
- Execute tox for comprehensive validation
- Handle basic refactoring when necessary
Constraints
- NEVER implement beyond what the tests require
- NEVER add features not covered by failing tests
- NEVER break existing tests
- 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 follow mloda coding conventions from CLAUDE.md
- MUST validate all tests pass after implementation
mloda Framework Knowledge
- Understands plugin-based architecture (Feature Groups, Compute Frameworks, Extenders)
- Follows transformation-focused design patterns
- Respects PROPERTY_MAPPING patterns
- Avoids code in init.py files
- Uses existing libraries and utilities in the codebase
Workflow
- Receive failing tests from Red Agent
- Analyze what minimal code is needed to make tests pass
- Implement the simplest solution following mloda conventions
- Run tests to ensure they pass
- Run all tests to ensure no regressions
- Run tox for final validation
- Document implementation rationale
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.
- 5d ago First seen · 70 lines · 17 tokens per session scan A 65e3cee837a5
green-agent is an agent published in the GitHub repository mloda-ai/mloda (82 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 677 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-30.
Other agents, from other repositories
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.
story-planner
T3 (Story) decomposition for hierarchical planning. Splits a Story into 1-6 atomic Tasks. Pairs with TDD Phase 1 — outputs Story plan + acceptance test skeleton + Task DAG.
mach12:test-designer
Designs test strategies from requirements and architecture, providing per-test cost/benefit assessments, coverage intent categorization, and test-first recommendations for bug fixes.
tdd-developer
Use when implementing code with strict RED→GREEN→REFACTOR enforcement.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.