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 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/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/motlin/claude-code-plugins/openrewrite-violations"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/openrewrite-violations.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.00055 | $0.00596 |
| Opus 5.5 | $0.00022 | $0.00238 |
| Sonnet 5.5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
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 22d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix OpenRewrite Violations
Create a branch named openrewrite-violations (or the name the user supplies), then apply every configured OpenRewrite recipe that has violations one at a time, one commit per recipe, with the message Fix violations of OpenRewrite rule: <recipe>.
Follow the java:maven-cli skill for Maven, and the git:commit skill for commits.
Start from a clean checkout
Run git status --porcelain. If there are uncommitted changes, stop and tell the user: this workflow creates commits and must start clean. Do not stash, discard, or absorb their work.
Branch from the fetched upstream default branch:
git fetch origin
git switch -c openrewrite-violations origin/HEAD
Use git worktree add instead if the user is mid-work on another branch and their checkout should not move.
Find the recipes with violations
Follow the discovery, dry-run, and leaf-recipe sections of the java:openrewrite-analyze-recipes skill: the mise and justfile conventions, the rewrite-dry-run / rewrite <RECIPE> recipes, the profile flag, and the -Drewrite.pomCacheEnabled=false workaround all apply here. Treat each distinct named leaf recipe as one rule.
Present the ordered list to the user before applying changes.
Apply and commit each recipe
In a stable order, run each recipe in isolation against the tree left by the previous commits:
mise exec -- just rewrite <recipe>
# or: mise exec -- mvn rewrite:run -Drewrite.activeRecipes=<recipe> -Drewrite.pomCacheEnabled=false
- Skip a recipe that produces no changes; an earlier one may have covered it. Never create an empty commit.
- Stage only the files that recipe changed.
- Run the repository's required checks for the change.
- Commit with
Fix violations of OpenRewrite rule: <fully-qualified-recipe>.throughgit:commit.
Verify the cumulative branch
After all commits, build and test the whole project (mise exec -- just test, or mvn verify). A recipe that applies cleanly in isolation can still break the cumulative tree, so this check is mandatory.
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.
- 22d ago Changed · -27 lines 970867ef3dcf
- 1mo ago Changed · +33 lines 84743ea045c0
- 1mo ago 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 (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 596 once invoked, about $0.0002 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-04.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.