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 viknesh20-20/claude-code-tool-kit --skill wireframegit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/wireframe)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/wireframe"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/wireframe/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/viknesh20-20/claude-code-tool-kit/wireframe"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/wireframe.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.00047 | $0.01451 |
| Opus 5.5 | $0.00019 | $0.00580 |
| Sonnet 5.5 | $0.00009 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
wireframe 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 1mo 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wireframe
Produce wireframes that engineers can build from and reviewers can give feedback on without opening Figma. Pixel-free, structure-first, optimized for clarity over fidelity.
When to use
- Spec'ing a new screen before any visual design work.
- Documenting an existing screen's structure for the team.
- Comparing 2–3 layout options without committing to visual design.
- Onboarding a new dev/designer to the product's IA.
- Working on a project where Figma isn't part of the workflow.
When NOT to use
- After visual design has shipped and you need pixel-accurate review (use Figma / screenshots).
- For animations / interactions — those need a different artifact.
- For brand work — that's color, type, voice, not structure.
Operating method
1. Confirm what you're wireframing
- Single screen or whole flow? Multi-screen flows belong to
/design-flow; this skill is per-screen. - What states? Default, loading, empty, error — pick the relevant ones. Don't wireframe states that don't matter for this screen.
- What's the responsive context? Desktop / tablet / mobile / all three?
- What's the device? Web / native iOS / native Android / TV / wearable. Conventions differ.
2. Pick a notation
Three notations the toolkit supports. Pick what serves the screen.
A. ASCII boxes — best for layouts with clear regions
┌─ Header ────────────────────────────────────────────┐
│ Logo | Search | ⚙ 👤 Avatar │
└─────────────────────────────────────────────────────┘
┌─ Sidebar ─┐ ┌─ Main ──────────────────────────────┐
│ Inbox 3 │ │ ┌─ Today ──────────────────────┐ │
│ Sent │ │ │ • Sarah — Re: Q4 plan │ │
│ Drafts │ │ │ • System — Backup OK │ │
│ Starred │ │ │ • Marcus — New designs │ │
│ + New │ │ └───────────────────────────────┘ │
└───────────┘ │ │
│ ┌─ Yesterday ───────────────────┐ │
│ │ ... │ │
│ └───────────────────────────────┘ │
└─────────────────────────────────────┘
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.
- 1mo ago First seen · 172 lines · 47 tokens per session scan A ce3a9de4237e
wireframe is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 1,451 once invoked, about $0.0002 per session on Opus 5.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
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
frontend-design
Use this as the design-lead layer for VideoStudio COMPOSE work. It shapes project/composition/composition-manifest.json::artdirection and the model-authored HTML/SVG motion graphics in index.html.
ui-design-source
Use this skill when the user provides Figma material, design-export files, screenshots of design tools, PDFs, JSON, existing HTML or other UI source code, or asks for design-to-HTML/code fidelity. It adapts OpenDesign/Figma handoff discipline for UIDesigner without requiring a live source runtime.
design-system-importer
Use this when COMPOSE or an AUTO compose segment has any external reference media or style source: a reference image, reference video, DESIGN.md, brand guide, screenshot, existing website, design notes, or an explicit named visual direction.
ui-design-contract
Use this skill before rendering when the direction must persist across multiple screens/components, brand or system work, conflicting references, formal handoff, or a genuinely vague visual system. Ordinary single-screen screenshots and clear briefs use ui-design-executor's compact source/visual thesis instead of…
ui-design-system
Use this skill when creating, extending, or auditing a product UI system. It adapts Better Design-style design-system discipline without requiring an external runtime package.