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.
git clone --depth 1 https://github.com/Vvlladd/qrspi-orchestratorWrote 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/commands/vvlladd/qrspi-orchestrator/qrspi-loop)<a href="https://agentmods.dev/commands/vvlladd/qrspi-orchestrator/qrspi-loop"><img src="https://agentmods.dev/badge/commands/vvlladd/qrspi-orchestrator/qrspi-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/commands/vvlladd/qrspi-orchestrator/qrspi-loop"><img src="https://agentmods.dev/badge/commands/vvlladd/qrspi-orchestrator/qrspi-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.00051 | $0.00464 |
| Opus 5 | $0.00026 | $0.00232 |
| Sonnet 5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
qrspi-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 10d 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.
What it actually says
/qrspi-loop — minimal-scope QRSPI entry
This is not a separate pipeline. It is /qrspi entered in minimal-scope mode. Same agents,
same progress.md/tasks.json state bridge, same human gates, same verifier backend logic.
Run the QRSPI pipeline for: $ARGUMENTS
Apply these defaults:
- Scope mode = minimal. The
clarifierassesses scope at Q and proposes which phases to skip (typically R and S for a localized bug/one-file change). The skip is a recommendation you confirm at the gate — never automatic. Trivial-looking bugs can have non-trivial fixes. - Bug mode = on when the input describes a defect. The Implement loop must reproduce first: write a test that fails because of the bug, confirm RED, and only then fix. That test is the loop's exit oracle and ships as the regression guard.
- Loop the Implement phase (builder → verifier → builder) until the first of:
GREEN→ human gate (review diff) → PR phase- iteration cap (~4) → escalate: "can't converge, likely mis-scoped" → back to planner
- same
failureSignaturetwice → escalate: "stalled, no progress" - touched denylist (signing,
.xcconfig, migrations, entitlements, CI yml) → escalate now
- Verifier backend is chosen by host, not here: native Xcode 27 tools if in-IDE, XcodeBuildMCP if external. The loop never loads both.
If the clarifier finds the work is actually large (multi-module, ambiguous design), it should say
so and recommend promoting to a full /qrspi run rather than forcing the minimal path.
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.
- 10d ago First seen · 30 lines · 51 tokens per session scan A c34cb84142c1
qrspi-loop is a command published in the GitHub repository Vvlladd/qrspi-orchestrator (6 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 464 once invoked, about $0.0003 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-31.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).