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 jl-cmd/claude-dev-env --skill pr-plain-language-cleanupgit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWrote 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/jl-cmd/claude-dev-env/pr-plain-language-cleanup)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/pr-plain-language-cleanup"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/pr-plain-language-cleanup.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.00032 | $0.00776 |
| Opus 5 | $0.00016 | $0.00388 |
| Sonnet 5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
pr-plain-language-cleanup 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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR plain-language cleanup
Balance compression and readability
Shorten changed prose and make it easier to scan. Both matter.
- Word count: record before and after counts and the delta. Count changed prose only. Exclude code, frontmatter, and unchanged lines.
- Readability: check sentence length, order, headings, jargon, and dense blocks. Edit only when the result is easier to read.
- Diff churn: count changed lines. Remove whitespace-only movement and reflow-only churn.
- Meaning: preserve behavior, APIs, data, test intent, conditions, warnings, error detail, context, and public names.
Reflow is allowed only when it materially improves scanability after a real trim. Report the four results separately.
Review and trim this pull request:
If no link is given, find the clear PR in the current context. If none is clear, ask for one.
Read the full PR, full diff, every changed file, changed tests and docs, and all repo rules that apply.
Find the changed files. Send one capable agent to each file. If there are more files than agents, use small batches.
Each agent owns one file. Read every line. Review code, tests, names, comments, docstrings, strings, notes, Markdown, and examples.
Trim filler, repeats, vague words, needless code, needless names, dead notes, jargon, and steps that add no value. Use few words and small words.
Keep real behavior, checks, data, error detail, context, tests, and public names unless a safe full rename is clear. Do not change behavior for style. Do not shorten a name when it loses meaning.
Follow the repo rules:
- Name modules for their capability.
- Name functions for their action.
- Name variables for the value they hold.
- Name classes for what they are.
- Use capability names for shared code.
- Keep workflow words on workflow code.
- Keep comments and docs true to the code.
- Use real data and real behavior in tests.
Hard limits
This is a non-material, text-only trim.
DO NOT:
- run
e-simplify,e-code-review, orsource-command-sr-loop; - run
pr-cleanup,pr-refinement,pr-small-cl, placement audits, extraction audits, or capability-name audits; - run review loops, advisor gates, commit gates, promotion gates, or any other extra cleanup;
- hunt bugs, change behavior, change APIs, change data, add features, or split the PR;
- turn a text trim into a code fix.
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.
- 7d ago First seen · 94 lines · 32 tokens per session scan A 73bc3e3d995f
pr-plain-language-cleanup is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 776 once invoked, about $0.0002 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 skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…