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/clodexnpx skills add jdpalumbo2/workbench --skill clodexgit 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)<a href="https://agentmods.dev/skills/jdpalumbo2/workbench/clodex"><img src="https://agentmods.dev/badge/skills/jdpalumbo2/workbench/clodex.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.00085 | $0.12108 |
| Opus 5 | $0.00043 | $0.06054 |
| Sonnet 5 | $0.00017 | $0.02422 |
| Haiku 4.5 | $0.00009 | $0.01211 |
Grade A, and why
clodex scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
snap = json.loads(subprocess.check_output(["python3", state, "rebuild", run_dir])) How it starts
The opening of the file, as written. The whole thing — 869 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clodex — the front door
Overview
One entry point for all work, so nobody has to remember stage names. This skill runs five things in order and then hands off:
- Preflight — prove the environment before a stage burns tokens on it.
- Open-run detection — a run already in flight is resumed, never overwritten.
- Profile — load
.clodex/profile.json, or interview once and write it. - Lane classification — feature-shaped work enters the core path; every other shape is named and handed back, because those lanes are v0.2.
- Change boundary — record what was already dirty, and never let the run commit someone else's work.
Then it opens the run and hands to a stage skill.
This skill does not edit code, does not call Codex, and does not run release actions. The stage skills own all three.
Paths and commands
CLODEX_HOME="${CLODEX_HOME:-$HOME/.claude/skills/clodex}" # the dir holding this SKILL.md
STATE="$CLODEX_HOME/state/clodex_state.py"
REPO="$(git rev-parse --show-toplevel)"
cd "$REPO" # do this, do not just assume it
REMOTE="$(git rev-parse --abbrev-ref '@{upstream}' 2>/dev/null | cut -d/ -f1 || true)"
[ -n "$REMOTE" ] || REMOTE="$(git remote | head -1)" # empty = this repo has no remote
Shell variables do not survive between separate command invocations, so
re-establish this block at the top of any shell you run these procedures in.
Later sections use $REPO, $STATE, and $REMOTE as if it were already there.
Every command below runs from $REPO. git check-ignore, the repo
inspection in §3, and git add all resolve relative paths against the current
directory, so from a subdirectory they answer the wrong question — a correct
.gitignore reads as missing. If a step cannot cd, use git -C "$REPO" ….
| Thing | Path | Committed? |
|---|---|---|
| Run-state engine | $STATE |
catalogue |
| Profile schema | $CLODEX_HOME/profile.schema.json |
catalogue |
| Codex runner (stages only, never here) | $CLODEX_HOME/runner/run-codex.sh |
catalogue |
| Repo profile | $REPO/.clodex/profile.json |
yes |
| Run directory | $REPO/.clodex/<run-id>/ ($RUN_DIR below) |
no — gitignored |
What ships with it
17 files 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.
- profile.schema.json 11 KB
- README.md 7.6 KB
- runner/envelope.schema.json 7.8 KB
- runner/run-codex.sh 20 KB runs code
- runner/test_runner.sh 33 KB runs code
- runner/validate_envelope.py 11 KB runs code
- state/clodex_state.py 42 KB runs code
- state/fixtures/legacy-run.events.ndjson 24 KB
- state/fixtures/legacy-run.snapshot.json 26 KB
- state/fixtures/pilot-run.events.ndjson 26 KB
- state/reducer.py 18 KB runs code
- state/schemas/event.schema.json 5.5 KB
- state/schemas/snapshot.schema.json 9.8 KB
- state/test_clodex_state.py 53 KB runs code
- templates/handoff.md 3.6 KB
- templates/lane-brief.md 5.2 KB
- templates/lane-report.md 2.8 KB
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 · 869 lines · 85 tokens per session scan A 2e78746794ae
clodex is a skill published in the GitHub repository jdpalumbo2/workbench (1 stars, last pushed 12d ago), licensed MIT. It adds 85 tokens to every session and 12,108 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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".