Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Ryan-M-Frank/volley/plugin install volleyWrote 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/ryan-m-frank/volley/diagnose)<a href="https://agentmods.dev/skills/ryan-m-frank/volley/diagnose"><img src="https://agentmods.dev/badge/skills/ryan-m-frank/volley/diagnose/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/ryan-m-frank/volley/diagnose"><img src="https://agentmods.dev/badge/skills/ryan-m-frank/volley/diagnose.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.00049 | $0.01223 |
| Opus 5 | $0.00024 | $0.00611 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
diagnose 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 9d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/volley:diagnose
One-shot diagnosis of whether Volley is wired up correctly here. Run each check, print a [PASS]/[FAIL]/[WARN] line, and end with a remediation list for anything not green.
Steps for Claude
-
Codex CLI present. Run
codex --version. PASS if it prints a version >= 0.129; FAIL otherwise (remedy:npm install -g @openai/codex). -
Bundled Codex MCP reachable. Check whether the
mcp__codex__codextool is available this session. PASS if available; WARN if not (remedy:/reload-pluginsor restart Claude Code, since the plugin's bundled server may not have loaded yet). -
Platform terminal available. Detect the OS and check for a usable terminal launcher:
case "$(uname -s)" in Darwin*) command -v osascript >/dev/null && echo "[PASS] macOS terminal (osascript)" || echo "[FAIL] osascript missing" ;; Linux*) { command -v gnome-terminal || command -v kitty || command -v tmux; } >/dev/null \ && echo "[PASS] Linux terminal (gnome-terminal/kitty/tmux)" \ || echo "[FAIL] no gnome-terminal/kitty/tmux - install one or use VOLLEY_PLATFORM=tmux" ;; MINGW*|MSYS*|CYGWIN*) command -v wt >/dev/null && echo "[PASS] Windows Terminal (wt)" || echo "[FAIL] wt missing - install Windows Terminal" ;; *) echo "[WARN] unrecognized OS; set VOLLEY_PLATFORM=tmux for the universal fallback" ;; esac -
Plugin assets intact. Confirm the bundled scripts resolve:
for f in scripts/lib.sh scripts/spawn-codex.sh scripts/platforms/windows.sh scripts/platforms/macos.sh scripts/platforms/linux.sh scripts/platforms/tmux.sh; do [ -f "${CLAUDE_PLUGIN_ROOT}/$f" ] && echo "[PASS] $f" || echo "[FAIL] missing $f" done -
Per-repo lock state. If
.volley/STATEexists, report it and whether the named process is alive; otherwise note the repo isn't initialized:if [ -f .volley/STATE ]; then active=$(grep -E '^ACTIVE=' .volley/STATE | cut -d= -f2) task=$(grep -E '^TASK=' .volley/STATE | cut -d= -f2) pid=$(grep -E '^PID=' .volley/STATE | cut -d= -f2) echo "[INFO] lock: ACTIVE=$active TASK=$task PID=$pid" if [ -n "$pid" ] && [ "$pid" != "0" ]; then kill -0 "$pid" 2>/dev/null && echo "[INFO] named PID $pid is alive" \ || echo "[WARN] named PID $pid is dead - lock may be stale; run /volley:unlock if it's stuck" fi else echo "[WARN] .volley/ not initialized here - run /volley:setup" fi
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.
- 9d ago First seen · 70 lines · 49 tokens per session scan A 98f4e977001f
diagnose is a skill published in the GitHub repository Ryan-M-Frank/volley (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,223 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-31.
Other skills, from other repositories
systematic-debugging
4-phase root cause process + passive behavior auto-detection + L1→L4 pressure escalation (includes root-cause-tracing, defense-in-depth, condition-based-waiting techniques).
root-cause
Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
x-bug2rag
A knowledge-capture tool that turns reusable bug explanations into a local RAG collection, meaning a searchable store of text that an agent can retrieve later. It records the trigger, incorrect implementation, correct implementation, and observable difference.
x-cr
A software-correctness investigation skill for finding why code behaves differently from what was expected. It uses evidence from code paths, specifications, tests, logs, and changes to assess possible causes.