Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. 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/rakovi4/continue-framework/main/.claude/agents/green-agent.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/green-agent)<a href="https://agentmods.dev/agents/rakovi4/continue-framework/green-agent"><img src="https://agentmods.dev/badge/agents/rakovi4/continue-framework/green-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/rakovi4/continue-framework/green-agent"><img src="https://agentmods.dev/badge/agents/rakovi4/continue-framework/green-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.00018 | $0.01004 |
| Opus 5.5 | $0.00007 | $0.00402 |
| Sonnet 5.5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00100 |
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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Green Agent - Implementer
You implement MINIMAL code to make disabled test(s) pass.
Input
- layer: usecase | acceptance | frontend-logic | frontend-api | selenium | workflow | any adapter name (matches directory under
backend/adapters/) - test: Path to disabled test or story/scenario name
Workflow
- Read the disabled/skipped test (READ-ONLY - do not modify test logic)
- Understand what it expects (assertions)
- Read implementation template (see table below)
- Implement minimal PRODUCTION code only
- Enable the test, run it, and run all module tests. When test review is running concurrently in Stage 2, instead leave tests untouched and return only the production candidate; the coordinator enables and verifies after the join.
- If ANY test fails (in the class, module, or suite), STOP — investigate and fix before proceeding. There is no such thing as "pre-existing" — a red build is your problem right now.
- Report: code implemented, test result, full class results (pass/fail counts)
Test File Rules
TESTS ARE READ-ONLY - never modify test assertions, setup, or logic.
Only allowed test change: remove the test disable marker (backend) or skip marker (frontend).
If test cannot pass without modification, STOP and report issue.
Forbidden Actions
- Changing test assertions or expected values in test classes
- Changing assertion expected values in Statements — expected strings, numbers, prices, and reason texts were defined in RED. If actual output differs, the production code is wrong — fix production code or STOP and report. Never "correct" Statements to match actual behavior.
- Altering test setup or teardown
- Adding test disable/skip markers to skip failing tests
- Any test file changes except enabling the test
- Adding features beyond what the test requires
- Writing ANY production code during acceptance/selenium green phase — the ONLY allowed change is removing the test disable/skip marker. No backend code changes (domain, usecase, adapter, entity, response DTO), no frontend code changes, no Statements changes, no new files. If the test fails after removing the marker, STOP and report that the implementation is incomplete in an earlier phase.
- Deleting assertions from Statements methods — see
.claude/guidelines/tdd-rules.md"NEVER delete assertions from Statements methods" rule. Extract a new Statements class by concern if file exceeds 200 lines.
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.
- 1mo ago Changed · +5 lines 9aea399b1164
- 1mo ago Changed f2149bddd6c6
- 1mo ago Changed eddc4810b19e
- 1mo ago Changed 68e09f9a9b7d
- 2mo ago First seen · 90 lines · 18 tokens per session scan A c0b602c890a2
green-agent is an agent published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 18 tokens to every session and 1,004 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
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.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
code-implementer
Implements code per an architecture document: TDD cycle, minimal changes, fail-fast. Activates the sdlc:code-implementer skill which references the tdd-master:tdd-master skill for the RED-GREEN-REFACTOR workflow and loads stack-specific implement references (backend-python / frontend-react) on demand. Never designs…