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 commands/koolamusic/claudefiles/tunegit clone --depth 1 https://github.com/koolamusic/claudefilesWrote 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/koolamusic/claudefiles/tune)<a href="https://agentmods.dev/commands/koolamusic/claudefiles/tune"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/tune.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.00986 |
| Opus 5 | $0.00028 | $0.00493 |
| Sonnet 5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
tune 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 4d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adjust the visual intensity dial. Three directions, one skill.
First: Use the ux skill for design principles and anti-patterns.
MANDATORY PREPARATION
Gather context: target audience, brand personality/tone, and existing design direction. If you can't infer these confidently from the codebase, STOP and ask via AskUserQuestion. Guessing leads to generic AI slop.
Pick the direction
$ARGUMENTS determines the mode:
- bolder — Amplify safe or boring designs. More impact, more personality, more drama.
- quieter — Tone down aggressive designs. More refined, more sophisticated, easier on the eyes.
- colorize — Add strategic color to monochromatic designs. More warmth, more meaning, more engagement.
- empty — Assess the interface and recommend which direction.
Bolder
Increase visual impact while maintaining usability. "Bolder" means distinctive and confident, not chaotic.
WARNING: AI slop trap — when making things "bolder," don't default to cyan/purple gradients, glassmorphism, neon accents, or gradient text. These are generic, not bold.
- Typography: Replace generic fonts with distinctive choices. Extreme scale jumps (3-5x, not 1.5x). Pair 900 weights with 200 weights.
- Color: Increase saturation. Bold palette with unexpected combinations. Let one color own 60%. Tinted neutrals.
- Space: Extreme scale jumps. Break the grid intentionally. Asymmetric layouts. Generous whitespace (100-200px gaps).
- Effects: Dramatic shadows for elevation. Texture and depth (grain, halftone, duotone). Custom decorative elements.
- Motion: Staggered entrance choreography. Scroll-triggered effects. Satisfying hover feedback. Use ease-out-quart/quint/expo, never bounce.
- Composition: Clear focal point with dramatic treatment. Full-bleed elements. Unexpected proportions (70/30, 80/20).
Quieter
Reduce visual intensity while maintaining character. "Quieter" means refined and sophisticated, not boring.
- Color: Reduce saturation to 70-85%. Soften palette to muted tones. Fewer colors, more neutrals. Tinted grays, never pure gray.
- Weight: Reduce font weights (900→600, 700→500). Decrease sizes where appropriate. Use space and weight for hierarchy instead of color.
- Simplification: Remove decorative gradients, shadows, patterns that don't serve purpose. Flatten layering. Clean up blur effects and glows.
- Motion: Shorter distances (10-20px not 40px). Remove decorative animations. Keep only functional motion. Reduce or remove if not clearly purposeful.
- Composition: Smaller scale jumps for calmer feel. Bring elements back to grid. Consistent spacing rhythm.
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.
- 4d ago First seen · 62 lines · 55 tokens per session scan A c00f04b0939a
tune is a command published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 5d ago), licensed MIT. It adds 55 tokens to every session and 986 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-08-30.
Other commands, from other repositories
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
template-ui
Design a Sent template-builder interface.
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.
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.
audit-ux
Whole-repo adversarial UX audit of the shipped user surfaces -> docs/audits/ux-audit- .md.