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.
npx agentmods add skills/ryan-m-frank/volley/setupnpx skills add Ryan-M-Frank/volley --skill setupgit clone --depth 1 https://github.com/Ryan-M-Frank/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/setup)<a href="https://agentmods.dev/skills/ryan-m-frank/volley/setup"><img src="https://agentmods.dev/badge/skills/ryan-m-frank/volley/setup.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 | $0.00071 | $0.01826 |
| Opus 5 | $0.00036 | $0.00913 |
| Sonnet 5 | $0.00014 | $0.00365 |
| Haiku 4.5 | $0.00007 | $0.00183 |
Grade A, and why
setup 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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/volley:setup
One-time installation of the Volley workflow.
Steps for Claude
-
Verify Codex is installed.
- Run:
codex --version— must succeed and print a version >= 0.129. - We do NOT run an explicit
codex loginprobe here; the exact auth-status subcommand varies by Codex CLI version and a missing/wrong subcommand could falsely report "not logged in." Instead, the MCP smoke test in step 4 will surface auth errors clearly when the bridge tries to call Codex. If the smoke test fails with an auth error, instruct the user to runcodex loginand retry.
- Run:
-
Confirm the bundled Codex MCP server is reachable.
- Volley bundles the Codex MCP server (see the plugin's
.mcp.json); you do NOT write a project.mcp.json. - Check whether the
mcp__codex__codextool is available in this session. - If it is NOT available, the plugin was just installed and its MCP server has not loaded yet. Tell the user:
"Run
/reload-plugins(or restart Claude Code) so Volley's bundled Codex server loads, then re-run/volley:setup." (Confirm the exact reload command against this Claude Code version if/reload-pluginsis not recognized.) Then STOP - do not continue until the tool is reachable. - If it IS available, continue.
- Volley bundles the Codex MCP server (see the plugin's
-
Scaffold
.volley/.- Create directory:
mkdir -p .volley - Copy template:
cp "${CLAUDE_PLUGIN_ROOT}/scripts/templates/HANDOFF.md" .volley/HANDOFF.md(only if.volley/HANDOFF.mddoesn't already exist - never overwrite) - Copy the managed checkpoint:
cp "${CLAUDE_PLUGIN_ROOT}/scripts/templates/CHECKPOINT.md" .volley/CHECKPOINT.md(only if it doesn't already exist - never overwrite; this is the Volley-managed cross-agent state file, distinct from the user-owned HANDOFF.md). - Copy the project config only if absent (never overwrite - the user may have customized it):
cp "${CLAUDE_PLUGIN_ROOT}/scripts/templates/config.json" .volley/config.json. An absentconfig.jsonmeans "today's default behavior"; the scaffolded defaults (model: inherit, no required context files) reproduce that. - Copy gitignore:
cp "${CLAUDE_PLUGIN_ROOT}/scripts/templates/gitignore" .volley/.gitignore(overwrite OK; this is internal). - Initialize STATE:
. "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh" && volley_state_write .volley/STATE claude idle 0 - Write machine-local state
.volley/local.jsonwith this repo's identity (gitignored - never committed). Derive identity with the lib helpers and write the JSON yourself (host-parsed - no jq):
Then create. "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh" ROOT=$(volley_repo_root); REMOTE=$(volley_repo_remote) echo "root=$ROOT remote=$REMOTE".volley/local.json(only if absent) as:{ "version": 1, "repository": { "canonicalRoot": "<ROOT>", "remote": "<REMOTE>" }, "modelOverrides": { "review": null, "implementation": null }, "roles": {} }
- Create directory:
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.
- 3d ago First seen · 81 lines · 71 tokens per session scan A 466e8cd529a6
setup is a skill published in the GitHub repository Ryan-M-Frank/volley (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,826 once invoked, about $0.0004 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
self-assessment
Interactive skill assessment with personalized learning path generation.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
source-command-ccguide-daily
Daily update check — official Anthropic docs diff + guide/CC releases digest.
source-command-ccguide-diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
source-command-changelog
View recent CHANGELOG entries.
engineering-fundamentals
Background knowledge for code quality. Applied when reviewing naming conventions, DRY, SOLID, function size, refactoring, or when junior asks "is this clean", "code review", "better way".