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/rockielab/rockie-codex/cleannpx skills add Rockielab/rockie-codex --skill cleangit clone --depth 1 https://github.com/Rockielab/rockie-codexWrote 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/rockielab/rockie-codex/clean)<a href="https://agentmods.dev/skills/rockielab/rockie-codex/clean"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-codex/clean.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.00114 | $0.01246 |
| Opus 5 | $0.00057 | $0.00623 |
| Sonnet 5 | $0.00023 | $0.00249 |
| Haiku 4.5 | $0.00011 | $0.00125 |
Grade A, and why
clean 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 5d 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.
This is a copy
92% identical to clean — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/clean — Pre-commit audit adapted for a research repo
Research repos are typically majority prose — scripts, experiment dirs,
and many .md docs read by humans AND future agents. Slop in either
kind hurts. The audit covers both.
When to run
- Before EVERY
git commit. Thepre-commit-gatehook will block if the sentinel hash doesn't match current staged state. - When the user asks to commit.
- When the hook emits a block message.
What the skill does
- Runs
${OPENCLAW_SKILLS_DIR}/clean/audit.py. Arguments:--scope staged(default) — audits files ingit diff --cached --name-only--scope dirty— audits all modified + untracked non-gitignored files
- The audit reports findings in three buckets:
- Blockers — must fix before commit (new
.mdfiles created during cleanup runs, broken internal doc links, obvious debug artifacts, syntax errors) - Warnings — should review (TODO markers pointing to resolved work,
duplicate content across docs, rules contradicting
${OPENCLAW_WORKSPACE_DIR}/memory/workflow.db) - Info — worth knowing (file size growth, complexity spikes)
- Blockers — must fix before commit (new
- If zero blockers: the audit invokes
${OPENCLAW_WORKSPACE_DIR}/scripts/clean-finalize.sh <hash>as its final action. That script writes${OPENCLAW_WORKSPACE_DIR}/.state/clean-ok-<hash>(where<hash>is computed by${OPENCLAW_WORKSPACE_DIR}/scripts/compute_clean_hash.sh) AND emits the upstream-contribute nudge to stderr. The pre-commit-gate hook recomputes the same hash and requires the sentinel to exist. - If blockers exist: the skill reports them and does NOT call
clean-finalize.sh, so no sentinel and no nudge. Agent fixes, reruns.
Hard rules for this repo specifically
- NEVER create new
.mdfiles during cleanup. Consolidate into existing ones. Exception: a user explicitly says "write a new doc for X." - NEVER auto-fix documentation. Flag it, let agent or user decide.
- NEVER audit the whole codebase. Only changed files. Existing slop elsewhere is not this commit's problem.
- Thresholds apply to NEW code only: Python funcs ≤ 80 lines, cyclomatic complexity ≤ 8. Existing violations are noise.
- Degrade gracefully: if
ruff/shellcheck/code-simplifierisn't installed, skip that check with a note. Don't block.
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.
- 5d ago First seen · 109 lines · 114 tokens per session scan A a122b4c6d96a
clean is a skill published in the GitHub repository Rockielab/rockie-codex (20 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 114 tokens to every session and 1,246 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to clean, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…