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/motlin/claude-code-plugins/openrewrite-violationsnpx skills add motlin/claude-code-plugins --skill openrewrite-violationsgit clone --depth 1 https://github.com/motlin/claude-code-pluginsWrote 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/motlin/claude-code-plugins/openrewrite-violations)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/openrewrite-violations"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/openrewrite-violations.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 | $0.00055 | $0.00548 |
| Opus 5 | $0.00028 | $0.00274 |
| Sonnet 5 | $0.00011 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
openrewrite-violations 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 yesterday.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix OpenRewrite Violations
Follow the Maven CLI skill for every Maven invocation and the repository's git workflow and commit skills for every commit.
Start from a clean checkout
Require git status --porcelain to be empty. Do not stash, discard, or absorb existing work.
Use the branch name supplied by the user, or openrewrite-violations by default. Fetch the upstream default branch and create the branch from its current tip. Prefer a new worktree when switching the user's active checkout would disrupt other work.
Discover the repository workflow
- Use mise for Maven and just commands when the repository configures it; trust the checked-in config first when required.
- Prefer repository-provided
rewrite-dry-runandrewrite <recipe>commands. - Otherwise inspect the rewrite Maven plugin, including profiles, and invoke
rewrite:dryRunorrewrite:rundirectly. - Never use Maven offline mode.
Capture the complete dry-run log in .llm/rewrite-dryrun.log. Treat "Applying recipes would make changes" as the expected violation signal. For a RocksdbMavenPomCache serialization failure, add -Drewrite.pomCacheEnabled=false and rerun.
Identify runnable recipes
Read the recipe tree preceding each changed file and collect distinct, most-specific named leaf recipes. Prefer a named wrapper over a raw parameterized recipe with inline options, which cannot be activated by name alone.
Present the stable ordered list before applying changes.
Apply and commit each recipe
For each recipe in order:
- Run that recipe alone with the repository command or
mvn rewrite:run -Drewrite.activeRecipes=<fully-qualified-recipe>. - Inspect and stage only the files changed by that recipe.
- Skip the recipe when it produces no changes; an earlier recipe may have covered it.
- Run the repository's required checks for the change.
- Commit with
Fix violations of OpenRewrite rule: <fully-qualified-recipe>.
Never create an empty commit. Keep every recipe's changes isolated in its own commit and do not push unless the user asks.
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.
- yesterday First seen · 48 lines · 55 tokens per session scan A 58bc760d9dc7
openrewrite-violations is a skill published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed today), licensed Apache-2.0. It adds 55 tokens to every session and 548 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…