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 hamzaPixl/pixl-ai --skill ralph-loop-crewgit clone --depth 1 https://github.com/hamzaPixl/pixl-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/hamzapixl/pixl-ai/ralph-loop-crew)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/ralph-loop-crew"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/ralph-loop-crew/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/hamzapixl/pixl-ai/ralph-loop-crew"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/ralph-loop-crew.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.00064 | $0.00834 |
| Opus 5.5 | $0.00026 | $0.00334 |
| Sonnet 5.5 | $0.00013 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
ralph-loop-crew 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill wraps the ralph-loop plugin with pixl-crew conventions: structured completion criteria, crew agent verification, and context packet output. Instead of raw iteration prompts, it sets up a disciplined loop with measurable exit conditions.
Step 1: Parse Task & Define Completion Criteria
From the user's task description (passed as argument or asked interactively):
- Extract the task — what needs to be done
- Define measurable completion criteria — concrete checks that prove the task is done
- Set iteration budget — default 5, max 15 (ask user if ambiguous)
Examples of completion criteria:
- "fix all lint errors" →
npx eslint . --max-warnings 0exits 0 - "make all tests pass" →
npm testexits 0 - "refactor to DDD" → no lint errors + tests pass + reviewer agent finds no issues
- "build the feature" → builds + tests pass + type-check passes
Step 2: Detect Project Tooling
Scan the project for available verification commands:
- package.json →
npm test,npm run lint,npm run build,npm run typecheck - Makefile →
make test,make lint,make check - pyproject.toml →
pytest,ruff check,mypy - Cargo.toml →
cargo test,cargo clippy
Build a verification command list from what's available.
Step 3: Write Ralph Loop Configuration
Create .claude/ralph-loop.local.md with the following structure:
---
iteration: 0
max_iterations: { budget }
task: "{task summary}"
---
## Task
{Full task description from user}
## Completion Promise
The loop is complete when ALL of the following pass:
{Numbered list of completion criteria with exact commands}
## Verification Commands
Run these after each iteration to check progress:
```bash
{verification commands, one per line}
```
Instructions
- Read this file at the start of each iteration to get current state
- Work on the task — make meaningful progress each iteration
- Run all verification commands
- Update the
iterationcount in frontmatter - If all completion criteria pass, announce completion
- If not, note what remains and continue next iteration
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 · 109 lines · 64 tokens per session scan A 4b8380c05ac5
ralph-loop-crew is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 834 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.