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 radumarias/xorio-claude-plugin --skill polishgit clone --depth 1 https://github.com/radumarias/xorio-claude-pluginWrote 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/radumarias/xorio-claude-plugin/polish)<a href="https://agentmods.dev/skills/radumarias/xorio-claude-plugin/polish"><img src="https://agentmods.dev/badge/skills/radumarias/xorio-claude-plugin/polish/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/radumarias/xorio-claude-plugin/polish"><img src="https://agentmods.dev/badge/skills/radumarias/xorio-claude-plugin/polish.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.00070 | $0.00540 |
| Opus 5.5 | $0.00028 | $0.00216 |
| Sonnet 5.5 | $0.00014 | $0.00108 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
polish 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.
What it actually says
Polish Workflow
Run the full polish pipeline on local changes (unstaged + staged git diff).
Step 1: Scope Check
Run git diff --stat HEAD to identify changed files. If no changes found, report "Nothing to polish" and stop.
Step 2: Code Simplification
Launch the pr-review-toolkit:code-simplifier agent on the local changes (git diff).
Present findings. Apply simplification suggestions that improve readability without changing behavior.
Step 3: Code Cleanup
Invoke the cleanup-code skill scoped to local changes only.
This handles: language detection, standards loading, cleanup analysis, refactoring with validation.
Step 4: Code Review
Launch the pr-review-toolkit:code-reviewer agent on the local changes.
Present findings. Fix any issues flagged.
Step 5: Security Audit
Launch the xorio:security-auditor agent scoped to changed files (git diff --name-only HEAD).
Fix any critical or high findings before finishing.
Step 6: Standards Validation
Launch the superpowers:code-reviewer agent (via Task tool) to validate all accumulated changes from Steps 2-5 against the project's coding standards and conventions.
Fix any findings.
Step 7: Final Validation
Run language-appropriate validation on changed files:
- Rust:
cargo fmt --all && cargo clippy --all-targets --all-features && cargo test - TypeScript:
npx biome check --write . && npx tsc --noEmit && npm test - Python:
ruff check --fix . && ruff format . && mypy . && pytest
Step 8: Update CLAUDE.md
Invoke claude-md-management:revise-claude-md (via Skill tool) to capture any learnings, patterns, or convention updates discovered during the polish process.
Step 9: Summary
Report:
- Files polished (count + list)
- Simplifications applied
- Cleanup changes made
- Review issues fixed
- Security findings addressed
- Standards validation status
- Final validation status (pass/fail)
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 · 63 lines · 70 tokens per session scan A 243ec4777666
polish is a skill published in the GitHub repository radumarias/xorio-claude-plugin (3 stars, last pushed 6d ago), licensed MIT. It adds 70 tokens to every session and 540 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
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"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…