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 Jerry0022/dotclaude --skill tune-polishgit clone --depth 1 https://github.com/Jerry0022/dotclaudeWrote 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/jerry0022/dotclaude/tune-polish)<a href="https://agentmods.dev/skills/jerry0022/dotclaude/tune-polish"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/tune-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/jerry0022/dotclaude/tune-polish"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/tune-polish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 48 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 49 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00174 | $0.04248 |
| Opus 5 | $0.00087 | $0.02124 |
| Sonnet 5 | $0.00035 | $0.00850 |
| Haiku 4.5 | $0.00017 | $0.00425 |
Grade A, and why
tune-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.
How it starts
The opening of the file, as written. The whole thing — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tune Polish — UI Refinement Pass
Refine the UI: consistency, visual polish, state-visuals, and UI-side
functionality — with user approval for structural changes. Scope: $ARGUMENTS.
Invocation Context
Same three invocation paths as /tune-harden:
- Direct — user types
/tune-polish. - From
/run-agents— pass--invoked-by=agentsplus--parent-mode=background|interactive. Skip self-spawned qa/redteam if parent owns those waves. Structural changes (Step 10) STILL require approval — when--parent-mode=background, structural items are skipped + flagged for parent's report. - From
/run-autonomous— pass--invoked-by=autonomous(implies--autonomous). No permission priming, no user prompts. Structural changes always flagged for the autonomous report (never auto-applied).
The Single-Agent Shortcut from deep-knowledge/agent-orchestration.md
applies: orchestrators delegate directly to this skill instead of building
a wave for polish-tasks (avoids double qa/redteam spawning).
Step 0 — Load Extensions
Check for optional overrides. Use Glob to verify each path exists before reading. Skip missing files silently.
- Global:
~/.claude/skills/tune-polish/SKILL.md+reference.md - Project:
{project}/.claude/skills/tune-polish/SKILL.md+reference.md - Merge order: project > global > plugin defaults
Project extensions can declare:
- Allowed design tokens (spacing scale, color tokens, typography ramp)
- Brand rules (forbidden hardcoded colors, required icon sizes)
- Layout conventions (button positions, form patterns)
Step 1 — Parse Arguments
Scan $ARGUMENTS for:
--autonomousflag → set$AUTONOMOUS=1. Skips ALLAskUserQuestioncalls. Structural changes are STILL not auto-applied — they get flagged in the final report. Autonomous is mute mode, not yolo mode.--invoked-by=agents|autonomous→ set$PARENT_SKILL. See "Invocation Context".--invoked-by=autonomousimplicitly sets$AUTONOMOUS=1.--parent-mode=background|interactive→ only with--invoked-by=agents. Background acts like--autonomous.- Any remaining tokens → treat as scope path(s).
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 · 378 lines · 174 tokens per session scan A 8ef06775cd9f
tune-polish is a skill published in the GitHub repository Jerry0022/dotclaude (5 stars, last pushed today), licensed MIT. It adds 174 tokens to every session and 4,248 once invoked, about $0.0009 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.