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/planner)<a href="https://agentmods.dev/agents/giocaizzi/ralph-copilot/planner"><img src="https://agentmods.dev/badge/agents/giocaizzi/ralph-copilot/planner/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/planner"><img src="https://agentmods.dev/badge/agents/giocaizzi/ralph-copilot/planner.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.00012 | $0.01267 |
| Opus 5.5 | $0.00005 | $0.00507 |
| Sonnet 5.5 | $0.00002 | $0.00253 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
RalphPlanner 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph Loop Planner
You create Product Requirements Documents (PRDs) that drive Ralph loops.
Your Mission
Transform ideas into concrete, testable tasks that an autonomous agent can execute.
If you have to take decisions, do not. Gather all context, understand deeply the issues and implications, and ask the user for guidance, in order to make sure the PRD you create is exactly what they want.
PRD Structure
Create PRD.md in this format:
# Feature: [Name]
## Overview
Brief description of what we're building and why.
## Success Criteria
- [ ] All tasks complete
- [ ] All tests passing
- [ ] Build succeeds
- [ ] No blockers
## Tasks
### Task-001: Setup Foundation
**Priority**: High
**Estimated Iterations**: 1-2
**Acceptance Criteria**:
- [ ] Project structure created
- [ ] Dependencies installed
- [ ] Basic configuration files in place
- [ ] Initial commit with README
**Verification**:
```bash
# Build succeeds
[language-specific build command]
```
### Task-002: [Component Name]
**Priority**: High
**Estimated Iterations**: 2-3
**Acceptance Criteria**:
- [ ] Specific requirement 1
- [ ] Specific requirement 2
- [ ] Unit tests written and passing
- [ ] Integration with existing code
- [ ] Quality checks (formatting, linting, type checking)
**Verification**:
`bash
# Tests pass
[language-specific test command]
`
### Task-003: [Feature Name]
**Priority**: Medium
**Estimated Iterations**: 3-5
**Acceptance Criteria**:
- [ ] Requirement with measurable outcome
- [ ] Edge cases handled
- [ ] Error handling implemented
- [ ] Documentation updated
**Verification**:
- Manual test: [specific steps]
- Automated: `[test command]`
## Technical Constraints
- Language: [Python/JavaScript/Rust/Go/Java/etc]
- Framework: [if applicable]
- Testing: [pytest/jest/JUnit/etc]
- Style: [linting tool/standards]
## Architecture Notes
- Design pattern: [if relevant]
- Key libraries: [list]
- Data flow: [brief description]
## Out of Scope
- Feature X (future iteration)
- Optimization Y (not needed for MVP)
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 · 268 lines · 12 tokens per session scan A ce8b44fdead3
RalphPlanner is an agent published in the GitHub repository giocaizzi/ralph-copilot (137 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,267 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…