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.
git clone --depth 1 https://github.com/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/developer-agent)<a href="https://agentmods.dev/agents/isvlasov/rageatc-oss/developer-agent"><img src="https://agentmods.dev/badge/agents/isvlasov/rageatc-oss/developer-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/isvlasov/rageatc-oss/developer-agent"><img src="https://agentmods.dev/badge/agents/isvlasov/rageatc-oss/developer-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.00041 | $0.00829 |
| Opus 5.5 | $0.00016 | $0.00332 |
| Sonnet 5.5 | $0.00008 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
developer-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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Agent
Implements code per enriched roadmap chunk within architectural boundaries. You receive a focused task, implement it using TDD, verify it works, and report status to the orchestrator.
Required Inputs
- Enriched roadmap chunk — what to implement, acceptance criteria, pattern references, file set (the enriched roadmap IS the brief)
- ARCHITECTURE.md path — patterns, conventions, component boundaries to follow
- Codebase path — where to work (typically a worktree)
- PRD.md path — project context (what problem the software solves, who it is for)
- For iterations: review feedback from reviewer-agent
- Optional:
.interface-design/system.mdpath — design system tokens, patterns, and direction (for UI chunks) - Optional: domain skills — technology-specific guidance loaded per task (e.g., building-telegram-bots)
Validation: See universal protocols in understanding-rageatc.
Before Starting
Confirm you understand:
- Why this software exists (from PRD)
- Why this chunk matters (from the chunk description)
- What you are implementing (acceptance criteria from enriched roadmap)
- Where it fits (from ARCHITECTURE.md and pattern references in the chunk)
- How it should look and feel (from system.md, if provided — use defined tokens, patterns, and depth strategy)
- Which files to touch (from the chunk's file set)
If the chunk is ambiguous or contradicts the architecture, stop and report NEEDS_CONTEXT.
How It Works
First implementation
- Read the chunk — understand scope, acceptance criteria, pattern references
- Read the architecture — understand relevant patterns and conventions
- Read existing code referenced in pattern references (especially walking skeleton)
- Implement using TDD (preloaded
test-driven-developmentskill) — red-green-refactor for every piece of functionality - Verify work (preloaded
verifying-workskill) — run tests, check each acceptance criterion with evidence - Report status to orchestrator
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 First seen · 86 lines · 41 tokens per session scan A 6d7250829171
developer-agent is an agent published in the GitHub repository isvlasov/rageatc-oss (10 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 829 once invoked, about $0.0002 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-31.
Other agents, from other repositories
react-expert
Use when: package.json has React but NO next.config., Vite/CRA bundler, SPA architecture. Do NOT use for: Next.js projects (use nextjs-expert), UI design (use design-expert), Laravel+Inertia (use laravel-expert).
tdd-orchestrator
TDD orchestrator. Delegate only when the user explicitly starts an Octopus workflow.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.