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/jdpalumbo2/workbench/clodex-plannpx 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.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.00060 | $0.11776 |
| Opus 5 | $0.00030 | $0.05888 |
| Sonnet 5 | $0.00012 | $0.02355 |
| Haiku 4.5 | $0.00006 | $0.01178 |
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 today.
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 — 916 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 "")')"
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.
$PLAN is empty until §6 records a plan; after that it is whatever the manifest
says, never a path you remember. §8 hands it to the runner, so a shell that
skipped this block passes --input '' and dies with usage error 64.
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.
- today Changed · +56 lines faa8b068bcc6
- 5d 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 2d ago), licensed MIT. It adds 60 tokens to every session and 11,776 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
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
map-wayfind
Decision-frontier wayfinding: build and work a durable map of open design decisions BEFORE planning, for large or foggy efforts where /map-plan would force premature decomposition. Use when a task is too big or too vague to decompose — many unknowns, tangled decisions, or "I'm not even sure what to build yet" — and…
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
clipboard
Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".