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 skills add devcodex-labs/devcodex --skill rework-prevention-engineeringgit clone --depth 1 https://github.com/devcodex-labs/devcodexWrote 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/devcodex-labs/devcodex/rework-prevention-engineering)<a href="https://agentmods.dev/skills/devcodex-labs/devcodex/rework-prevention-engineering"><img src="https://agentmods.dev/badge/skills/devcodex-labs/devcodex/rework-prevention-engineering/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/skills/devcodex-labs/devcodex/rework-prevention-engineering"><img src="https://agentmods.dev/badge/skills/devcodex-labs/devcodex/rework-prevention-engineering.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.00093 | $0.02604 |
| Opus 5.5 | $0.00037 | $0.01042 |
| Sonnet 5.5 | $0.00019 | $0.00521 |
| Haiku 4.5 | $0.00009 | $0.00260 |
Grade A, and why
rework-prevention-engineering 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 1mo 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
2 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.
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.
- 1mo ago First seen · 127 lines · 93 tokens per session scan A f28eb9cc8abb
rework-prevention-engineering is a skill published in the GitHub repository devcodex-labs/devcodex (438 stars, last pushed 6d ago), licensed AGPL-3.0. It adds 93 tokens to every session and 2,604 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other skills, from other repositories
vibe-coding-playbook
A lightweight engineering workflow for turning an idea into a real, shippable product with an AI coding agent. Core = Karpathy's four coding disciplines (think before coding / simplicity first / surgical changes / goal-driven; battle-tested), plus an Explore→Plan→Build→Polish→Ship process, task tiers (skip the process…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
browser-use
Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…