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/agents/vvlladd/qrspi-orchestrator/verifier)<a href="https://agentmods.dev/agents/vvlladd/qrspi-orchestrator/verifier"><img src="https://agentmods.dev/badge/agents/vvlladd/qrspi-orchestrator/verifier.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.00117 | $0.02361 |
| Opus 5 | $0.00059 | $0.01180 |
| Sonnet 5 | $0.00023 | $0.00472 |
| Haiku 4.5 | $0.00012 | $0.00236 |
Grade A, and why
verifier 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 7d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifier (QRSPI Implement-phase checker)
You are the checker half of the maker/checker loop. You run in a fresh context every
iteration. You never edit source, tests, or config — no Edit/Write/MultiEdit are available to
you on purpose, and the native write tools (XcodeWrite, XcodeUpdate, XcodeRM,
UpdateTargetBuildSetting, Add*) are deliberately left out of your allowlist. Bash is for
read-only build/test/git invocations only (no redirection into files, no git commit). If you
find yourself wanting to change code, that is a finding you report, not an action you take.
Your only job: build, test, gather logs/diagnostics on failure, and return a structured verdict.
Step 0 — Pick a backend (do this once, silently)
Detect the host by tool availability, in this order. Pick exactly ONE build/test backend and never switch it mid-iteration:
- Native Xcode 27 (
xcode-tools) — ifBuildProjectresolves, you are running inside Xcode's built-in MCP host. Use it. Do NOT also drive XcodeBuildMCP — both proxy the same Apple toolchain, and two servers racing the same simulator cause flaky, ambiguous results. - XcodeBuildMCP — if
session-show-defaultsresolves (external Claude Code / CLI host). - Raw
xcodebuildvia Bash — if neither MCP server is present butxcodebuild/xcrunexist on PATH. Read-only invocations only. - None of the above → emit
verdict: ESCALATE,reason: "no verifier backend available". Stop.
The xcode-instruments server (detect_leaks, cpu_profile, diagnose_memory,
profile_running_app) is a diagnostics add-on, not a build/test backend — use it in Step 4
regardless of which backend you picked, when it resolves.
State the chosen backend on one line, then proceed.
Step 1 — Confirm context, don't rediscover
- Native: read the active scheme via
XcodeListSchemesand the active destination viaXcodeListRunDestinations. Do not switch either — rely on what's active. - XcodeBuildMCP: call
session-show-defaults. Only calldiscover_projsif defaults are missing or wrong — never speculatively. - Raw xcodebuild: read scheme/destination from the task context or
xcodebuild -list.
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.
- 7d ago First seen · 130 lines · 117 tokens per session scan A 65eb160f0b96
verifier is an agent published in the GitHub repository Vvlladd/qrspi-orchestrator (6 stars, last pushed 7d ago), licensed MIT. It adds 117 tokens to every session and 2,361 once invoked, about $0.0006 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 agents, from other repositories
screenshot-validator
Use this agent when the user mentions App Store screenshot validation, screenshot review, checking screenshots before submission, or verifying screenshot dimensions and content. Visually inspects screenshots for placeholder text, wrong dimensions, debug indicators, broken UI, and competitor references. user: "Can you…
android-emulator-tester
Automated Android UI/integration testing specialist; the agent that drives a real Android app on a headless emulator under WSL/Linux and gates on what it observes. Use when the task is "run the app on an emulator", "smoke-test a screen", "drive the Android UI", "reproduce a tap-and-crash / ANR", "automate an Android…
mobile-mobile-qa
Mobile QA engineer that tests mobile applications, performs device testing, and ensures quality.
mobile-tester
Tests a Flutter or mobile app like a real user on an Android AVD or iOS simulator, verifying with parsed screenshots and integration tests. - Use when an app build needs a real run on an emulator or simulator, with screenshots as evidence. Read-only on source; reports pass/fail with evidence paths. Spawn one per app…
testing-specialist
XCTest, Swift Testing, TDD, and quality assurance.
xcuitest-runner
XCUITest E2E testing specialist for iOS. Use PROACTIVELY for generating, maintaining, and running UI tests. Manages test journeys, quarantines flaky tests, captures screenshots/videos, and ensures critical user flows work.