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/status)<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>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.00066 | $0.01110 |
| Opus 5 | $0.00033 | $0.00555 |
| Sonnet 5 | $0.00013 | $0.00222 |
| Haiku 4.5 | $0.00007 | $0.00111 |
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.
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
-
Verify
.volley/exists. If not, tell user to run/volley:setupfirst and stop. -
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 -
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 -
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)" -
Read continuity config for the report (non-mutating). If
.volley/config.jsonexists, parse it (host JSON, no jq) and resolve the review/implementationmodel+reasoningEffort(inherit→ show "Codex default"). If.volley/local.jsonexists, 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". -
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>
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.
- 6d ago First seen · 78 lines · 66 tokens per session scan A f544906c564f
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.
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.
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.
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.
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…
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…
shipyard-handoff
Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress.