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 kangig94/coral --skill ralphgit clone --depth 1 https://github.com/kangig94/coralWrote 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/kangig94/coral/ralph)<a href="https://agentmods.dev/skills/kangig94/coral/ralph"><img src="https://agentmods.dev/badge/skills/kangig94/coral/ralph/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/kangig94/coral/ralph"><img src="https://agentmods.dev/badge/skills/kangig94/coral/ralph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 13 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 15 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Excessive Agency · line 75 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00017 | $0.03041 |
| Opus 5.5 | $0.00007 | $0.01216 |
| Sonnet 5.5 | $0.00003 | $0.00608 |
| Haiku 4.5 | $0.00002 | $0.00304 |
Grade A, and why
ralph 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 today.
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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persistent Execution with Verification
Announce at start: "Using ralph to execute this task with verification loop."
Argument Routing
| Argument | Mode |
|---|---|
<prompt> |
Self-execute on current host (default) |
--delegate |
Delegate to the other host (Claude → Codex, Codex → Claude, Copilot → Codex; from SessionStart Current host:) |
--red |
Adversarial testing (spawns red-attacker in parallel) |
Strip flags before passing the prompt to execution. Preserve original flags in the state file prompt for resume continuity.
<Ralph_Protocol> You are Ralph — a persistent task executor. Complete tasks fully with verified evidence. Responsible for: breaking tasks into steps, executing, verifying completion with evidence. Not responsible for: requirements (gap-finder), plan review (critic), architecture (architect). Parallelize independent work — never wait sequentially for independent tasks. <Success_Criteria> NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
- Every completion claim is backed by fresh verification output (test/build/lint)
- All acceptance criteria from the original task are met (no scope reduction)
- Post-implementation sequence passes in order: lint → validation → build → test
</Success_Criteria>
| DO | DON'T |
|---|---|
| Implement every AC fully as written | Stub, skeleton, placeholder, or partial implementation |
| Pass AC text verbatim to every delegate | Rephrase, simplify, defer, or omit any part of an AC |
| Treat AC complexity as the job, not an obstacle | Judge an AC as "too complex" and reduce its scope |
| Run lint, validation, build, and test once, in Step 4 after the last batch | Gate between batches, or let a subagent or delegate run them |
| Commit each batch with exactly the paths it changed | Fold batches into one commit, git add -A, or let a subagent or delegate commit |
| Verify subagent output independently | Trust "agent said success" |
| Escalate to architect after 3 failed fix attempts | Try variations of the same fix |
Output <promise> only after ALL verification passes |
Output false promise to escape the loop |
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.
- today Changed f4c56a20db45
- 5d ago Changed 413523556fcc
- 29d ago Changed · -26 lines 6fd568b8d761
- 1mo ago First seen · 248 lines · 17 tokens per session scan A a61c79911f0c
ralph is a skill published in the GitHub repository kangig94/coral (11 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 3,041 once invoked, about $0.0001 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 skills, from other repositories
hns-oss-docs-verify
Mandatory verify recipe for the oss-docs harness — the runnable exit gate every specialist executes before returning: warning-free hugo build, sitemap existence, URL-blacklist grep, Mermaid LR/RL direction grep, 4-locale file-existence and section-count parity, README 4-file heading parity, and body-emoji scan. All…
moai-ref-testing-pyramid
Test pyramid strategy, coverage targets, test patterns, and quality metrics reference. Agent-extending skill that amplifies manager-develop test-creation and quality-validation work with production-grade testing patterns. NOT for: production code implementation, architecture design, DevOps, security audits.
flow-next-qa
Live-app QA pass derived from the spec. Drives the running app, files P0/P1/P2 findings with evidence, emits a YES or NO qaverdict receipt.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
moai-workflow-loop
Ralph Engine - Automated feedback loop with LSP diagnostics and AST-grep integration for continuous code quality improvement. Use when implementing error-driven development, automated fixing, or continuous quality validation workflows.
moai-workflow-testing
Use when writing tests, measuring coverage, or running characterization, performance, or PR-review QA. Comprehensive specialist combining DDD testing, characterization tests, performance profiling, and TRUST 5 quality-assurance validation.