Borrowing it
Nothing to install: this file belongs to terrene-foundation/metis. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/terrene-foundation/metis/main/.claude/commands/i-polish.mdgit clone --depth 1 https://github.com/terrene-foundation/metisWrote 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/commands/terrene-foundation/metis/i-polish)<a href="https://agentmods.dev/commands/terrene-foundation/metis/i-polish"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/i-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/commands/terrene-foundation/metis/i-polish"><img src="https://agentmods.dev/badge/commands/terrene-foundation/metis/i-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.00000 | $0.01137 |
| Opus 5 | $0.00000 | $0.00568 |
| Sonnet 5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $0.00114 |
Grade A, and why
i-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 9d 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.
This is a copy
95% identical to i-polish — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/i-polish - Visual Refinement Workflow
Purpose
Systematically fix aesthetic and visual quality issues identified by /i-audit. Takes audit findings in dimensions 1-7 and applies concrete fixes to typography, color, spacing, interaction, and motion.
Part of the Impeccable pipeline: /i-audit (diagnose) → /i-polish (refine) → /i-harden (fortify)
Usage
| Command | Action |
|---|---|
/i-polish |
Full visual refinement pass on current file/component |
/i-polish $ARGUMENTS |
Focused refinement on a specific area (e.g., typography, color, motion) |
Refinement Process
Step 1: Context Gathering (Mandatory)
Before refining, gather:
- What framework? (React, Flutter, vanilla HTML/CSS)
- What component/page? (Read the target files)
- Existing design system? (Check for design tokens, theme files)
- Audit results? (Check if
/i-auditwas run — use those scores to prioritize)
If no audit exists, run /i-audit first to establish a baseline.
Step 2: Systematic Refinement (7 Areas)
Work through each area, prioritizing by audit score (lowest scores first):
1. Visual Hierarchy
- Apply size/weight/position formula: primary > secondary > tertiary
- Ensure important elements draw attention first
- Fix competing focal points
2. Information Architecture
- Apply 70/30 rule (core content vs. supporting)
- Implement progressive disclosure for complexity
- Group related elements logically
3. Typography
- Establish modular type scale (e.g., 1.25 ratio: 12, 15, 19, 24, 30, 37)
- Create weight contrast (not
font-weight: 600on everything) - Optimize line-height per context (headings: 1.1-1.3, body: 1.5-1.7)
- Set measure to 45-75 characters for readability
4. Color & Contrast
- Apply semantic color usage (meaning, not decoration)
- Verify WCAG AA contrast ratios (4.5:1 text, 3:1 large text)
- Remove decorative gradients and random accent colors
- Establish intentional palette with purpose for each color
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.
- 9d ago First seen · 137 lines · 0 tokens per session scan A cdab0cd0ff11
i-polish is a command published in the GitHub repository terrene-foundation/metis (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,137 tokens. A static security scan graded it A with 0 findings. It is 95% identical to i-polish, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
team-ui
Orchestrate UI/UX design team.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.