diagnose

diagnose is a skill for Claude Code from Ryan-M-Frank/volley. It costs 49 tokens per session (1,223 once invoked), scanned A, original, Apache-2.0.

A diagnostic command for checking whether the Volley environment is set up correctly. Volley is a workflow that coordinates Claude and Codex through a shared project state.

In plain words
What is it for?
Use it when setup misbehaves or when beginning a session in a new repository.
Why use it?
It identifies problems with the coding-agent command, communication bridge, terminal, or project lock before work starts.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions Claude Code; mentions Codex.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the volley plugin — 8 skills, 1 MCP server shipped together

Good fit Use it when setup misbehaves or when beginning a session in a new repository.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add Ryan-M-Frank/volley
Claude Code
/plugin install volley

Made for: Claude Code.

Or install volley, the plugin that ships this one along with the rest of its 8 skills, 1 MCP server.

Wrote 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.

agentmods badge for diagnose

README.md
[![agentmods](https://agentmods.dev/badge/skills/ryan-m-frank/volley/diagnose/github.svg)](https://agentmods.dev/skills/ryan-m-frank/volley/diagnose)
Your own site
<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.

agentmods 80×15 button for diagnose

Your own site · 80×15
<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>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 98f4e977001f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

skills/diagnose/SKILL.md · 70 lines

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

  1. Codex CLI present. Run codex --version. PASS if it prints a version >= 0.129; FAIL otherwise (remedy: npm install -g @openai/codex).

  2. Bundled Codex MCP reachable. Check whether the mcp__codex__codex tool is available this session. PASS if available; WARN if not (remedy: /reload-plugins or restart Claude Code, since the plugin's bundled server may not have loaded yet).

  3. 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
    
  4. 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
    
  5. Per-repo lock state. If .volley/STATE exists, 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
    

Read the full file on GitHub · 70 lines

Changes

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.

  1. 9d ago First seen · 70 lines · 49 tokens per session scan A 98f4e977001f

Subscribe to this mod's changes

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.

Related

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).

myths-labs/muse · 43 tokens

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.

jjanczur/tyran · 61 tokens

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…

DollarDill/beads-superpowers · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

DollarDill/beads-superpowers · 21 tokens

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.

KtKID/x-dev-pipeline · 255 tokens

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.

KtKID/x-dev-pipeline · 183 tokens