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 skills add jdpalumbo2/workbench --skill clodex-plangit clone --depth 1 https://github.com/jdpalumbo2/workbenchWrote 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/jdpalumbo2/workbench/clodex-plan)<a href="https://agentmods.dev/skills/jdpalumbo2/workbench/clodex-plan"><img src="https://agentmods.dev/badge/skills/jdpalumbo2/workbench/clodex-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jdpalumbo2/workbench/clodex-plan"><img src="https://agentmods.dev/badge/skills/jdpalumbo2/workbench/clodex-plan.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.13460 |
| Opus 5.5 | $0.00024 | $0.05384 |
| Sonnet 5.5 | $0.00012 | $0.02692 |
| Haiku 4.5 | $0.00006 | $0.01346 |
Grade A, and why
clodex-plan 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 14d 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 — 1,004 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clodex-plan — ground, decide, get an approved plan
Overview
This stage owes the run exactly four things, all of them facts in the run's event log:
- A plan file in the repo, at the profile's plans directory.
plan:recorded(orplan:amended) carrying that file's version, path, and sha256 hash.- Every plan-review finding disposed —
fixed,accepted,rejected, ordeferred-to-build. verification:declaredfor each evidence class, thenplan:approvedbound to the current plan hash.
When those exist, the plan is approved and clodex-build can start.
Where this stage ends. You declare owned paths and done when per batch.
clodex-build composes the full batch contract from them (forbidden paths,
test expectations) and executes. You never write code, never open a batch, and
never commit anything at all — clodex-ship commits run-owned paths.
You arrive here from clodex, which owns preflight, the profile, lane
classification, the change boundary, and the run directory. If you were invoked
without an absolute run directory, stop and invoke clodex — do not go
looking for a run yourself.
0. Paths and commands
CLODEX_HOME="${CLODEX_HOME:-$HOME/.claude/skills/clodex}" # the router's dir, not this one
STATE="$CLODEX_HOME/state/clodex_state.py"
RUNNER="$CLODEX_HOME/runner/run-codex.sh"
RUN_DIR="<the absolute run dir the router handed you>"
SNAP="$(python3 "$STATE" rebuild "$RUN_DIR")"
REPO="$(printf '%s' "$SNAP" | python3 -c 'import json,sys;print(json.load(sys.stdin)["repo"])')"
PLAN="$(printf '%s' "$SNAP" | python3 -c 'import json,sys;print(json.load(sys.stdin)["plan"]["path"] or "")')"
LANE="$(printf '%s' "$SNAP" | python3 -c 'import json,sys;l=json.load(sys.stdin).get("lane") or "standard";print("standard" if l=="feature" else l)')" # a pre-0.6 run (feature) takes the standard table
cd "$REPO"
PROFILE="$REPO/.clodex/profile.json"
Shell variables do not survive between command invocations — re-establish this
block at the top of every shell you run these procedures in. Everything below
runs from $REPO.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed · +17 lines 4b9126028f92
- 24d ago Changed · +62 lines 583585757596
- 1mo ago Changed · +9 lines 7d2a6b43d5de
- 1mo ago Changed · +56 lines faa8b068bcc6
- 1mo ago First seen · 860 lines · 60 tokens per session scan A c0b797f3cfcc
clodex-plan is a skill published in the GitHub repository jdpalumbo2/workbench (1 stars, last pushed 15d ago), licensed MIT. It adds 60 tokens to every session and 13,460 once invoked, about $0.0002 per session on Opus 5.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
codex-autoresearch
Run repeated, measured Git experiments toward a numeric target; keep improvements and revert failures. Use for autonomous optimization or managing an autoresearch run, not one-shot edits.
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
flue
Let agents control software, like Adobe Photoshop, Illustrator, After Effects, Premiere, Autodesk 3DS Max, Blender, Unity, Houdini, and Microsoft Office.
code-that-fits-in-your-head
Software-engineering heuristics based on Mark Seemann's Code That Fits in Your Head (2021), updated for agent-driven development. Use when writing or reviewing code, refactoring accidental complexity or a Big Ball of Mud, controlling technical or architectural debt in generated code, designing APIs and invariants…
rexai-image-generation
An image-generation skill that uses RexAI to create new images from text or transform existing images from other images. It returns the result as a local file.