Borrowing it
Nothing to install: this file belongs to tomdwipo/claude-soul. 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/tomdwipo/claude-soul/main/.claude/commands/wireframe-image.mdgit clone --depth 1 https://github.com/tomdwipo/claude-soulWrote 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/tomdwipo/claude-soul/wireframe-image)<a href="https://agentmods.dev/commands/tomdwipo/claude-soul/wireframe-image"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/wireframe-image.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.1 | $0.00000 | $0.00506 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
wireframe-image 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 8d 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
Create a detailed ASCII wireframe diagram from a design mockup image.
Instructions:
-
Analyze the provided design image carefully
-
Identify all UI elements, their hierarchy, and layout structure
-
Create a visual ASCII wireframe showing:
- Screen sections with borders and boxes
- Top bar/navigation (if present)
- All UI components with descriptive labels
- Icons represented with emoji or text descriptions
- Spacing and padding indicators (e.g., [16dp space])
- Color annotations (e.g., <- Blue border, Teal button)
- Text content from the design (preserve actual text)
- Component boundaries and containers
-
Include a comprehensive "Layout Specifications" section with:
- Structure Hierarchy: Tree format showing nested components
- Design Tokens:
- Colors (with semantic names like charcoal800, oceanBlue500)
- Typography (h1, h2, bodyMedium, etc. with sizes)
- Spacing (padding, margins in dp)
- Shapes (corner radius, borders)
- Components Used: List of Compose components needed
- Behavior & Interactions: Click actions, navigation, states
-
Add an "Insight" section with header format "INSIGHT:" explaining:
- Screen purpose and user journey context
- Design patterns used (Progressive Disclosure, Information Hierarchy, etc.)
- Layout strategy and why components are positioned this way
- UX considerations (accessibility, user flow, error prevention)
- Notable design decisions (dual exit paths, visual hierarchy, etc.)
-
Formatting requirements:
- Use box-drawing characters for clean borders: ╭─╮ │ ╰─╯ or +--+ | +--+
- Include arrow annotations (<- or ->) for explanations
- Mark interactive elements clearly
- Preserve actual text content from the design
- Use text descriptions for icons when appropriate (e.g., [Email Icon] [Headset Icon] [Chat Icon])
-
Do NOT create any code implementation
-
Focus on visual representation and design documentation
-
DO NOT add any recommended improvements or suggestions for the design. just follow the instruction.
Output format:
- Title with screen name
- ASCII art wireframe with detailed annotations
- Hierarchical structure diagram
- Complete design token specifications
- Component and behavior documentation
- Educational insights section
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.
- 8d ago First seen · 50 lines · 0 tokens per session scan A d04866f7d033
wireframe-image is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 506 tokens. 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
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.
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.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
team-ui
Orchestrate UI/UX design team.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.