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/reshapegit 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/reshape)<a href="https://agentmods.dev/commands/koolamusic/claudefiles/reshape"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/reshape.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.00042 | $0.01096 |
| Opus 5 | $0.00021 | $0.00548 |
| Sonnet 5 | $0.00008 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
reshape 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Restructure an interface without changing its visual identity. Three modes.
First: Use the ux skill for design principles and anti-patterns.
MANDATORY PREPARATION
Gather context: target audience, use cases, and what's truly essential vs nice-to-have. If you can't infer these confidently, STOP and ask via AskUserQuestion.
Pick the mode
$ARGUMENTS:
- responsive — Adapt to work across screen sizes, devices, and input methods
- simplify — Strip to essence, remove unnecessary complexity
- extract — Pull reusable components and design tokens into the design system
- empty — Assess the interface and recommend which mode
Responsive
Rethink the experience for each context. Adaptation is not just scaling.
Mobile (320-767px):
- Single column, vertical stacking, full-width components
- Bottom navigation, hamburger for complex nav
- Touch targets 44px min, thumb-first design
- Progressive disclosure, shorter text, 16px minimum
- Swipe gestures where appropriate, bottom sheets over dropdowns
Tablet (768-1023px):
- Two-column, master-detail, side panels
- Support both touch and pointer
- Adaptive based on orientation
Desktop (1024+):
- Multi-column, side navigation always visible
- Hover states, keyboard shortcuts, right-click menus, drag-and-drop
- Max-width constraints (don't stretch to 4K)
- Show more information upfront, richer visualizations
Techniques:
- CSS Grid/Flexbox for layout reflow
- Container queries for component-level adaptation
clamp()for fluid sizing- Responsive images (
srcset,picture) - Content-driven breakpoints over generic ones
Print/Email: If applicable — proper page breaks, inline CSS for email, narrow width (600px max), table-based email layouts.
Never: Hide core functionality on mobile. Use different IA across contexts. Forget landscape orientation. Use generic breakpoints blindly.
Test on real devices, not just browser DevTools.
Simplify
Remove obstacles between users and their goals. Simplicity is not feature-less — it's obstacle-less.
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 · 108 lines · 42 tokens per session scan A 7044cc7ac1b6
reshape is a command published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 1,096 once invoked, about $0.0002 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
tokens
Audit or establish the project's 3-layer token spine.
bolder
Amplify personality — raises layout variance and motion, strengthens typography and one signature detail, without slop. Use when the UI works but feels safe, flat, or "template-y", or when the user says "bolder", "more personality", "more creative", or "make it pop" (still professional).
motion-design
Design micro-interactions, transitions, and animation systems for UI components or full pages.
ux-motion
Animation and motion rubric. Checks timing, easing, meaning, reduced-motion compliance, and performance for every animation on a surface. Triggers on "motion check", "are the animations good", or "fix the motion". Use when auditing motion or animations, checking durations / easing / reduced-motion / performance, is…
ux-recommend
The v2 flagship. Runs the 5-parallel-search Python engine across 11 data manifests (75+ styles, 170+ palettes, 65+ type pairs, 120+ components, 170+ industries, 110+ UX laws, 50+ motion presets, 120+ anti-patterns, 92 brand specs) and returns a complete recommended design system for your project — with always-on…
review-css-complexity
Scan codebase for overly complex CSS/styling patterns that should be simplified.