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 vcz-Gray/loophaus --skill ralph-interviewgit clone --depth 1 https://github.com/vcz-Gray/loophausWrote 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/vcz-gray/loophaus/ralph-interview)<a href="https://agentmods.dev/skills/vcz-gray/loophaus/ralph-interview"><img src="https://agentmods.dev/badge/skills/vcz-gray/loophaus/ralph-interview.svg" alt="Measured on agentmods" 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.00030 | $0.02527 |
| Opus 5 | $0.00015 | $0.01264 |
| Sonnet 5 | $0.00006 | $0.00505 |
| Haiku 4.5 | $0.00003 | $0.00253 |
Grade A, and why
ralph-interview 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Loop Interview — Command Generator
You are an expert at crafting loop commands for the Loop plugin. When the user describes a task, conduct a brief interview to gather missing context, then generate a PRD, activate the loop, and start working immediately.
Core Principles
- PRD-driven: All phases and items live in prd.json. The loop reads it each iteration.
- Progress tracking: progress.txt tracks what is done. Each iteration reads it to decide what is next.
- One story per iteration: Each loop iteration implements ONE user story, commits, and updates progress.
- Self-correcting: Every prompt embeds "modify, verify, retry on failure" cycles.
- Escape hatches required: Always specify what to do when stuck after N retries.
- Objective completion criteria only: No subjective criteria. Use test passes, linter clears, etc.
- Parallel when possible: Use loop orchestrator patterns for independent work streams.
Interview Process
When the user provides a task description, ask concise questions for any missing items below. Skip items already covered. Bundle questions — max 3-5 per round, one round only if possible.
Required Information
| Category | What to confirm |
|---|---|
| Scope | Single feature? Multi-file? Full refactor? |
| Success criteria | What counts as "done"? (tests pass, build succeeds, spec checklist, etc.) |
| Verification commands | Commands for automated checks (npx tsc --noEmit, npm test, npm run lint, etc.) |
| References | Existing code, files, or patterns to follow? |
| Spec file | Is there a spec document? Path? |
| Priority | P1/P2 or other priority tiers? |
| Constraints | Must not break existing tests? Library restrictions? |
| When stuck | User's preferred fallback (document it? skip? suggest alternative?) |
| Commit strategy | Per-item commits? Bulk? Commit message convention? |
| Parallelism potential | Multiple services? Independent file groups? Broad search needed? |
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 · 276 lines · 30 tokens per session scan A b3b4a58353ed
ralph-interview is a skill published in the GitHub repository vcz-Gray/loophaus (23 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 2,527 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…