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/giocaizzi/ralph-copilot/executorgit clone --depth 1 https://github.com/giocaizzi/ralph-copilotWhat 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.00011 | $0.01395 |
| Opus 5 | $0.00005 | $0.00698 |
| Sonnet 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 yesterday.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,395 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
agent_types
This document describes how the unified three-layer Device Agent architecture is implemented across different platforms. While the core framework (State, Processor, Command layers) remains consistent, each platform implements specialized agents optimized for their native control mechanisms and hierarchies.…
server_client_architecture
Device agents in UFO are partitioned into server and client components, separating high-level orchestration from low-level execution. This architecture enables safe, scalable, and flexible task execution across heterogeneous devices through the Agent Interaction Protocol (AIP).
builder
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…
finalize
Snapshot visual QA + one in-place fix pass + render. Dispatched only when Step 6 lint/inspect reports issues, or to do the final render.
f1-test-drive
Orchestrate F1 test drives to validate the Cyrus agent system end-to-end. Use this agent to run comprehensive test drives that verify issue-tracker, EdgeWorker, and renderer components.
lead
Use this agent to orchestrate a full task from the harness backlog: decompose it into a plan, delegate to explorer, builder, and reviewer in sequence, and close the session correctly. Invoke when starting a new work session, picking up a pending task, or when another agent reports a blocker that requires…