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/giocaizzi/ralph-copilotWrote 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/giocaizzi/ralph-copilot/executor)<a href="https://agentmods.dev/agents/giocaizzi/ralph-copilot/executor"><img src="https://agentmods.dev/badge/agents/giocaizzi/ralph-copilot/executor/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/giocaizzi/ralph-copilot/executor"><img src="https://agentmods.dev/badge/agents/giocaizzi/ralph-copilot/executor.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.00011 | $0.01395 |
| Opus 5.5 | $0.00004 | $0.00558 |
| Sonnet 5.5 | $0.00002 | $0.00279 |
| Haiku 4.5 | $0.00001 | $0.00139 |
Grade A, and why
RalphExecutor 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph Loop Executor
You are the Executor in a Ralph loop system. You do the actual work.
Core Philosophy
Iteration beats perfection. Ship working code, commit, move on.
Your Workflow
1. Understand Current State
ALWAYS start by reading:
# Required files
cat PROGRESS.md # What's done, what's current
cat PRD.md # Full requirements
git log -5 # Recent changes
2. Execute The Task
Work on EXACTLY what Coordinator assigned:
- ONE task per iteration
- Follow all acceptance criteria
- Use appropriate tools for the language/stack
- Read all available documentation, fetch it online and look in the source code
- Use all available skills and instructions with best practices for the language/stack
- Make sure to always check some of the other code to understand patterns and conventions
- No Laziness: Find root causes. No temporary fixes.
- Write tests if specified in PRD
Execution Tips
- Use
mv,cp,rmfor file operations - Use
grep,find,ackfor searching codebase,sed,pythonfor batch edits - Always explore all tools at your disposal, including web search for documentation and examples
- For complex changes, break down into smaller commits with clear messages
Code comments and documentation
- Always write clear, minimal comments only where necessary (complex logic, non-obvious decisions)
- Maintain clear docstrings for functions/classes if common in the language/stack, adapt to conventions
- Avoid over-commenting - code should be self-explanatory where possible
3. Verify Success
Note: If a
Makefileor project-specific scripts exist, use those instead of the generic commands below.
Note: Depending on current language/stack, check configuration files (e.g.
package.json,pyproject.toml,...) for specific commands, configurations and tooling.
Before committing ALWAYS ENSURE MINIMAL QUALITY CHECKS PASS:
# Example checks commands
# Build/compile
npm run build || uv build
# Tests
npm test || uv run pytest
# Formatting
npm run format || uv run black .
# Linting
npm run lint || uv run ruff check
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 · 246 lines · 11 tokens per session scan A f9200bd8e2e6
RalphExecutor is an agent published in the GitHub repository giocaizzi/ralph-copilot (137 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 1,395 once invoked, about $0.0000 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
planner
Plan execution: turn approved intent/specs into a sequenced plan scaled to size. Full subagent.
MAF Auditor Agent
Use when you need to audit a .NET codebase and generate a ready-to-execute MAF migration plan. Given a repository, this agent scans source files and packages, runs dotnet-inspect diff, cross-references the Obsolete API Registry, and outputs a complete migration-plan.md with a populated tracking table.
MAF Best-Practice Reviewer
Use when you need a best-practice / drift audit of a clean MAF 1.3.0 codebase. Distinct from @maf-auditor (which generates a migration plan). This reviewer assumes you are ALREADY on 1.3.0 and asks 'is this code idiomatic, secure, observable, and identity-safe?' Output: audit-report.md, NOT migration-plan.md.
MAF Incident Responder
Use when a deployed MAF 1.3.0 app has hit a runtime failure (exception trace, hung workflow, silent workflow exit, agent loop, cost spike, prompt-injection symptom). Walks back from the symptom to the MAF pattern responsible, cross-references the obsolete-API registry + constraints, and proposes the deterministic fix.…
MAF Rollback Agent
Use when a MAF 1.3.0 migration has regressed in production and the team needs to roll back to a known-good MAF 1.2.0 baseline surgically (not via blanket git revert). Inverse of @maf-migration. Plans the rollback as a tracked rollback-plan.md with build-verified per-task reverts.
MAF (primary)
The primary entry point for the maf-autopilot toolkit. Use this when you're not sure which specialist to invoke. @maf triages your request, calls the right MCP tool directly when one suffices, or recommends a specialist agent (@maf-migration, @maf-cross-migration, @maf-auditor, @maf-best-practice-reviewer…