status

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

A read-only status skill for the Volley workflow, which coordinates Claude and Codex work in a repository. It reports the active task, lock age, process status, and recent review files.

In plain words
What is it for?
Use it to inspect Volley’s current lock and task state, check Codex’s process, and list recent review artifacts.
Why use it?
It helps determine whose turn it is, whether Codex is still running, and whether a lock may be stale without changing repository state.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: 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 to inspect Volley’s current lock and task state, check Codex’s…

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 status

README.md
[![agentmods](https://agentmods.dev/badge/skills/ryan-m-frank/volley/status.svg)](https://agentmods.dev/skills/ryan-m-frank/volley/status)
Your own site
<a href="https://agentmods.dev/skills/ryan-m-frank/volley/status"><img src="https://agentmods.dev/badge/skills/ryan-m-frank/volley/status.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,110 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.00066 $0.01110
Opus 5 $0.00033 $0.00555
Sonnet 5 $0.00013 $0.00222
Haiku 4.5 $0.00007 $0.00111

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

Security

Grade A, and why

status 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 6d 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/status/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/volley:status

Read-only inspection of the Volley state. Never modifies anything.

Steps for Claude

  1. Verify .volley/ exists. If not, tell user to run /volley:setup first and stop.

  2. Read STATE. Source the lib and read all four keys. If any key read fails (missing file, missing key, or malformed STATE), report the error to the user verbatim and stop - do NOT continue with empty/default values.

    . "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh"
    ACTIVE=$(volley_state_get .volley/STATE ACTIVE) || exit 1
    TASK=$(volley_state_get .volley/STATE TASK) || exit 1
    SINCE=$(volley_state_get .volley/STATE SINCE) || exit 1
    PID=$(volley_state_get .volley/STATE PID) || exit 1
    AGE=$(volley_state_lock_age .volley/STATE) || exit 1
    
  3. Check PID liveness if ACTIVE=codex.

    if [ "$ACTIVE" = "codex" ] && [ "$PID" != "0" ]; then
      if volley_state_pid_alive "$PID"; then PID_STATUS="alive"; else PID_STATUS="DEAD"; fi
    else
      PID_STATUS="n/a"
    fi
    
  4. List recent .volley/ artifacts. If no artifacts exist yet, show (no review artifacts yet) instead of a blank section.

    ARTIFACTS=$(ls -lt .volley/*.md 2>/dev/null | head -5)
    [ -z "$ARTIFACTS" ] && ARTIFACTS="(no review artifacts yet)"
    
  5. Read continuity config for the report (non-mutating). If .volley/config.json exists, parse it (host JSON, no jq) and resolve the review/implementation model + reasoningEffort (inherit → show "Codex default"). If .volley/local.json exists, note whether repo identity matches (volley_repo_identity_matches) and which roles have a stored thread/session id (presence only - never print the id or any secret). Absent files → report "defaults / not initialized".

  6. Report to user. Format like this:

    Volley Status
    ──────────
    Active actor:  <ACTIVE>
    Current task:  <TASK>
    Lock since:    <SINCE>  (<AGE>s ago)
    Recorded PID:  <PID>  (<PID_STATUS>)
    
    Continuity
    ──────────
    Review model:  <model / Codex default>  (effort: <effort>)
    Impl model:    <model / Codex default>  (effort: <effort>)
    Repo identity: <match | mismatch → will rehydrate | not initialized>
    Saved threads: planReview=<yes/no> prReview=<yes/no> implementation=<yes/no>
    Local state:   .volley/local.json   Checkpoint: <managedCheckpoint path>
    
    Recent artifacts:
    <ls output>
    

Read the full file on GitHub · 78 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. 6d ago First seen · 78 lines · 66 tokens per session scan A f544906c564f

Subscribe to this mod's changes

status is a skill published in the GitHub repository Ryan-M-Frank/volley (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,110 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.

Related

Other skills, from other repositories

delegate

Let Claude Architect route a versioned implementation spec through the trusted MCP runtime, independently review the Candidate Artifact, record a decision, and integrate only accepted bytes. Use for implementation delegation, Producer selection, or commitment-boundary review.

PyModel/claude-architect · 47 tokens

codex

Run the Codex CLI directly in the user's checkout for code analysis, refactoring, or automated editing without Claude Architect's verified delegation lifecycle.

PyModel/claude-architect · 31 tokens

commit

A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.

restarter/lets-workflow · 90 tokens

explain

Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do…

harnessprotocol/harness-kit · 95 tokens

design

Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…

cryndoc/polisade-orchestrator · 162 tokens

shipyard-handoff

Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress.

lgbarn/shipyard · 27 tokens