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-verifynpx skills add jdpalumbo2/workbench --skill clodex-verifygit 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-verify)<a href="https://agentmods.dev/skills/jdpalumbo2/workbench/clodex-verify"><img src="https://agentmods.dev/badge/skills/jdpalumbo2/workbench/clodex-verify.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.00055 | $0.11862 |
| Opus 5 | $0.00028 | $0.05931 |
| Sonnet 5 | $0.00011 | $0.02372 |
| Haiku 4.5 | $0.00006 | $0.01186 |
Grade C, and why
clodex-verify scanned grade C with 2 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
printenv SOME_API_TOKEN >/dev/null && echo "SOME_API_TOKEN is set" || echo "SOME_API_TOKEN is NOT set" 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 — 859 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clodex-verify — evidence per class, debt for the rest, no gate
Overview
This stage turns "the batches are committed" into proof, and it owes the run exactly two kinds of fact — both in the event log, neither in a transcript:
| Fact | Event | In the run manifest |
|---|---|---|
| a declared class was produced, and what showed it | verification:evidence |
verification.evidence[] |
| a declared class was not produced, why, and what that risks | verification:debt |
verification.debt[] |
Every class clodex-plan declared ends in exactly one of those two states.
Never neither, never both. §10 checks that property mechanically.
This stage has no gate
Verify records debt. It never accepts, waives, or blocks on it. There is no
"is this debt OK?" question in this document, and you must not invent one: a run
with three debt entries and a run with none both leave this stage the same way —
handed to clodex-ship.
Debt is accepted in exactly one place: clodex-ship's release
authorization, once, by the user, alongside the exact external actions they are
authorizing. That is the design's single binding debt gate. Asking the user to
approve debt here would double the gate and leave ship approving something
already half-approved — so you do not ask. You write it down, plainly, and you
say it out loud in the handoff.
Where this stage ends
You do not commit, you do not edit tracked files, and you do not fix code (§2).
You do not write the changelog, bump the version, tag, push, or deploy — that is
clodex-ship. You read the deploy block of the repo's committed profile
(<repo>/.clodex/profile.json) only to know what ship will do, never to do any
of it.
You arrive here from clodex or from clodex-build, which hands you an absolute
run directory. If you were invoked without one, 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 you were handed>"
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"
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 · +27 lines 5c065cac591a
- 5d ago First seen · 832 lines · 55 tokens per session scan C ae8f121e0869
clodex-verify is a skill published in the GitHub repository jdpalumbo2/workbench (1 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 11,862 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (harvests environment variables, 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".