implement

implement is a skill for Claude Code, Codex from Ryan-M-Frank/volley. It costs 92 tokens per session (3,197 once invoked), scanned A, original, Apache-2.0.

A workflow that hands an approved implementation plan to Codex to build. It checks the project’s Volley setup and state lock, then starts Codex with the plan and a progress-log location.

In plain words
What is it for?
Use it when a Volley plan is ready and Codex should implement it while logging work to .volley/IMPLEMENTATION-LOG.md.
Why use it?
It prevents implementation from starting when the shared workflow is not initialized or another agent is meant to control the source files. It also records progress during the build.

Skill for Claude CodeCodex

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/implement
Any agent
npx skills add Ryan-M-Frank/volley --skill implement
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.

Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,197 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.00092 $0.03197
Opus 5 $0.00046 $0.01598
Sonnet 5 $0.00018 $0.00639
Haiku 4.5 $0.00009 $0.00320

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

Security

Grade A, and why

implement 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/implement/SKILL.md · 181 lines

How it starts

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

/volley:implement

Hand the keys to Codex. Watch in another tab.

Steps for Claude

  1. Verify .volley/ is initialized and the lock allows Claude to act.

    [ -d .volley ] || { echo "ERROR: .volley/ not found. Run /volley:setup first." >&2; exit 1; }
    [ -f .volley/STATE ] || { echo "ERROR: .volley/STATE not found. Run /volley:setup first." >&2; exit 1; }
    . "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh"
    volley_state_assert_active .volley/STATE claude || exit 1
    
  2. Resolve the plan path.

    • If user passed an argument, use it.
    • Otherwise, find the latest PLAN.md (same logic as /volley:review-plan).
    • Read the plan content - we need to embed at least the path in Codex's prompt.
  3. Generate a per-run nonce and resolve absolute paths. The nonce makes the started marker unique per invocation, so a stale Codex from a prior run cannot satisfy this run's poll. The random component pulls 8 bytes (64 bits) from /dev/urandom, so collision probability is effectively zero - earlier $$ + $RANDOM versions left a small but real collision window for invocations from the same shell process within the same second.

    Both forms of each path matter: Bash uses POSIX-style for the poll/stat side, Codex runs on Windows and needs Windows-style paths in its prompt to create / read files reliably.

    NONCE=$(date -u +%Y%m%dT%H%M%SZ)-$(head -c 8 /dev/urandom | od -An -tx1 | tr -d ' \n')
    
    # POSIX-style absolute paths - used by the orchestrator (Bash) for stat/poll.
    PLAN_PATH=$(realpath <plan>)
    HANDOFF_PATH=$(realpath .volley/HANDOFF.md)
    CHECKPOINT_PATH=$(realpath .volley/CHECKPOINT.md)
    LOG_PATH=$(realpath .volley/IMPLEMENTATION-LOG.md)
    STATE_PATH=$(realpath .volley/STATE)
    STARTED_PATH=$(realpath .volley)/CODEX-STARTED-${NONCE}
    
    # Windows-style absolute paths - embedded in Codex's prompt because Codex
    # runs via `codex exec` on Windows, where Cygwin-style paths like
    # /c/git/... are not understood by native file tools.
    PLAN_PATH_WIN=$(cygpath -w "$PLAN_PATH")
    HANDOFF_PATH_WIN=$(cygpath -w "$HANDOFF_PATH")
    CHECKPOINT_PATH_WIN=$(cygpath -w "$CHECKPOINT_PATH")
    LOG_PATH_WIN=$(cygpath -w "$LOG_PATH")
    STATE_PATH_WIN=$(cygpath -w "$STATE_PATH")
    STARTED_PATH_WIN=$(cygpath -w "$STARTED_PATH")
    

Read the full file on GitHub · 181 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 · 181 lines · 92 tokens per session scan A 2525e3caa09d

Subscribe to this mod's changes

implement is a skill published in the GitHub repository Ryan-M-Frank/volley (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 92 tokens to every session and 3,197 once invoked, about $0.0005 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.