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 skills add saitarrun/Devforge-ai --skill ralph-loopgit clone --depth 1 https://github.com/saitarrun/Devforge-aiWrote 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/skills/saitarrun/devforge-ai/ralph-loop)<a href="https://agentmods.dev/skills/saitarrun/devforge-ai/ralph-loop"><img src="https://agentmods.dev/badge/skills/saitarrun/devforge-ai/ralph-loop/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/skills/saitarrun/devforge-ai/ralph-loop"><img src="https://agentmods.dev/badge/skills/saitarrun/devforge-ai/ralph-loop.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.00039 | $0.02024 |
| Opus 5 | $0.00019 | $0.01012 |
| Sonnet 5 | $0.00008 | $0.00405 |
| Haiku 4.5 | $0.00004 | $0.00202 |
Grade A, and why
ralph-loop 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 8d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph Loop Skill
A reusable self-diagnosing, self-correcting execution loop for the Build phase. Loaded by sdlc-build.md and sdlc-implement.md. Keeps token windows bounded by pinning only essential context on retries and routing targeted re-work rather than re-running everything.
Concepts
| Term | Definition |
|---|---|
| DoD | Definition of Done — the acceptance criteria for a slice, taken from its scope.json entry |
| Slice | One independently verifiable unit of work (a row in scope.json.slices[]) |
| Inner loop | Per-slice retry logic; runs inside the Build phase for each slice |
| Outer loop | Per-phase retry logic; runs once after qa-engineer's E2E pass |
| Sentinel | Lightweight health check that runs before the verification gateway to catch drift early |
| Circuit breaker | Hard limit on retries; surfaces failure to user rather than looping forever |
| Fresh context | Stripped-down context bundle assembled for each retry — no prior attempt reasoning |
Inner Loop (per-slice)
Runs for every slice in scope.json.slices[], in order.
┌─────────────────────────────────────────────────────┐
│ SLICE N ─ inner loop │
│ │
│ 1. Load DoD from scope.json slice entry │
│ 2. Assemble context bundle (see below) │
│ 3. SENTINEL CHECK ──► drift? → flag user, abort │
│ 4. fullstack-engineer executes slice │
│ 5. VERIFICATION GATEWAY │
│ run: typecheck + slice-scoped tests │
│ PASS ──► append to implementation-log.md │
│ advance to next slice │
│ FAIL ──► retry_count += 1 │
│ retry_count ≤ 2? ──► reassemble │
│ fresh context │
│ goto step 3 │
│ retry_count > 2? ──► CIRCUIT BREAKER │
│ surface to user │
└─────────────────────────────────────────────────────┘
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.
- 8d ago First seen · 196 lines · 39 tokens per session scan A 7314e4c2c3df
ralph-loop is a skill published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 28d ago), licensed Apache-2.0. It adds 39 tokens to every session and 2,024 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
zapier-demo
Walk a new user through setting up their first Zapier action and running it live — the smallest possible win. Asks what app they use, recommends one read action to enable, guides them to mcp.zapier.com to add it, then demonstrates it working in the same chat. Use when the user asks "show me how Zapier works", "set up…
zapier-status
Check the health of your Zapier MCP setup. Three modes — health check (dashboard view), audit (find waste and duplicates), diagnose (systematic troubleshooting). Use when asking "is my MCP working?", "check my tools", "audit my setup", "what's broken?", or "zapier status".
zapier-explore
Explore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions to make those use cases real. The natural next step after zapier-demo. Use when the user asks "what else can Zapier do…
zapier-onboard
Onboard a new user to Zapier MCP — introduce what it can do, walk through authentication, and route into the right flow based on the state of their setup. Use when getting started, troubleshooting connection issues, or when the user asks "what is Zapier MCP", "how do I get started with Zapier", "set me up", "what can…
agentic-data-science-competition
AI Agent-driven Kaggle competition workflow. Learn from real competition experience: score stabilization patterns, submission troubleshooting, kernel workflows, GPU task delegation, and the spec-driven development approach that achieved top leaderboard positions. Use when: working on any Kaggle competition, analyzing…
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it, or a sentence of editorial direction as a rider. Use when asked to work a ticket end-to-end.