setup

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

A one-time setup skill for the Volley workflow, which coordinates work between Claude and Codex in a repository. It checks the required tools, creates Volley’s tracking files, and runs a connection test.

In plain words
What is it for?
Use it when starting Volley in a repository to verify installation, create .volley files, and test the Codex bridge.
Why use it?
It prevents the workflow from being used before Codex, its connection, and the repository handoff files are ready.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

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

Install

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.

agentmods
npx agentmods add skills/ryan-m-frank/volley/setup
Any agent
npx skills add Ryan-M-Frank/volley --skill setup
Clone the repo
git clone --depth 1 https://github.com/Ryan-M-Frank/volley

Made for: Claude Code, Codex.

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 setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/ryan-m-frank/volley/setup.svg)](https://agentmods.dev/skills/ryan-m-frank/volley/setup)
Your own site
<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>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,826 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00071 $0.01826
Opus 5 $0.00036 $0.00913
Sonnet 5 $0.00014 $0.00365
Haiku 4.5 $0.00007 $0.00183

Measured 3d ago against content hash 466e8cd529a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

skills/setup/SKILL.md · 81 lines

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

  1. Verify Codex is installed.

    • Run: codex --version — must succeed and print a version >= 0.129.
    • We do NOT run an explicit codex login probe 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 run codex login and retry.
  2. 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__codex tool 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-plugins is not recognized.) Then STOP - do not continue until the tool is reachable.
    • If it IS available, continue.
  3. Scaffold .volley/.

    • Create directory: mkdir -p .volley
    • Copy template: cp "${CLAUDE_PLUGIN_ROOT}/scripts/templates/HANDOFF.md" .volley/HANDOFF.md (only if .volley/HANDOFF.md doesn'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 absent config.json means "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.json with this repo's identity (gitignored - never committed). Derive identity with the lib helpers and write the JSON yourself (host-parsed - no jq):
      . "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh"
      ROOT=$(volley_repo_root); REMOTE=$(volley_repo_remote)
      echo "root=$ROOT remote=$REMOTE"
      
      Then create .volley/local.json (only if absent) as:
      { "version": 1,
        "repository": { "canonicalRoot": "<ROOT>", "remote": "<REMOTE>" },
        "modelOverrides": { "review": null, "implementation": null },
        "roles": {} }
      

Read the full file on GitHub · 81 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. 3d ago First seen · 81 lines · 71 tokens per session scan A 466e8cd529a6

Subscribe to this mod's changes

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.