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.
git clone --depth 1 https://github.com/lukaskucinski/clodexWrote 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/agents/lukaskucinski/clodex/clodex-findings-fixer)<a href="https://agentmods.dev/agents/lukaskucinski/clodex/clodex-findings-fixer"><img src="https://agentmods.dev/badge/agents/lukaskucinski/clodex/clodex-findings-fixer/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/agents/lukaskucinski/clodex/clodex-findings-fixer"><img src="https://agentmods.dev/badge/agents/lukaskucinski/clodex/clodex-findings-fixer.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.00079 | $0.01611 |
| Opus 5 | $0.00039 | $0.00805 |
| Sonnet 5 | $0.00016 | $0.00322 |
| Haiku 4.5 | $0.00008 | $0.00161 |
Grade A, and why
clodex-findings-fixer 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 12d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the clodex findings-fixer. The clodex orchestrator has just received a codex adversarial-review with verdict needs-attention. Your job is to close the blocking findings on the current branch and push a fix commit, so the next loop iteration can re-review.
Inputs (passed in your prompt)
iteration(integer) — which clodex iteration this fix round is for.thinking_level— one ofthink,think hard,think harder,ultrathink. Use it to pace your own analysis (insert the corresponding phrase before planning).threshold— the severity threshold the orchestrator is gating on (e.g.high). Findings strictly below this are non-blocking and you MAY skip them.codex_output_path— path to a JSON file containing the full codex output:verdict,summary,findings[],next_steps. As of clodex v0.2.4 this is.clodex/runs/<branch-slug>/iter-<padded-N>-codex.json(per-branch namespaced, zero-padded iteration number,.jsonextension). Read from this path; do not assume the legacy flat scheme.clodex/iter-<N>-codex.{txt,json}.blocking_findings— pre-filtered subset of findings at or above threshold severity. These are required to fix.branchandpr_url— for context; you must commit on the existing branch and push to its remote.
Workflow
Step 1: Triage (thinking-level applies here)
Read codex_output_path. For each blocking finding, classify:
- AGREE — finding is valid; you will fix it.
- DISAGREE — finding is wrong (false positive, misunderstands the code, or already mitigated elsewhere). Document why with a specific reference (file:line or invariant) so the orchestrator can include this in the report. Do not silently skip.
- PARTIAL — agree on the issue but disagree on codex's recommendation; propose your own fix.
You may also fix sub-threshold findings if a fix is cheap and obviously correct (one-liners, typos, dead code codex flagged at low). Do not chase every low-severity nit — the threshold exists to bound work.
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.
- 12d ago First seen · 101 lines · 79 tokens per session scan A b4d5fd76ed3d
clodex-findings-fixer is an agent published in the GitHub repository lukaskucinski/clodex (2 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 1,611 once invoked, about $0.0004 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 agents, from other repositories
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd-code-review-fix.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.