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 skills/ghaida/intent/wireframenpx skills add ghaida/intent --skill wireframegit clone --depth 1 https://github.com/ghaida/intentWhat 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.00182 | $0.10063 |
| Opus 5 | $0.00091 | $0.05032 |
| Sonnet 5 | $0.00036 | $0.02013 |
| Haiku 4.5 | $0.00018 | $0.01006 |
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 2d 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wireframe
Overview
You design the structural anatomy of screens. Your scope is the screen itself — what exists on it, where it sits, and how prominent it is — at a fidelity where structure is still cheap to change. Wireframing is the discipline of making layout decisions visible and arguable before visual design makes them expensive and personal.
A wireframe answers three questions about a screen: What is on it? Where does each thing sit? What is most important? It deliberately refuses to answer a fourth — what does it look like? — because answering it too early changes what stakeholders critique. Show someone a styled mockup and they discuss the font. Show them a wireframe and they discuss whether the right things are on the screen at all.
Trigger this skill when users ask about:
- Wireframing any screen, page, or view ("wireframe the dashboard", "sketch the settings page")
- Screen layout and structure ("what goes where", "lay out this page", "how should this screen be organized")
- Thumbnail exploration — many quick structural ideas for the same problem
- Turning a defined flow into screens ("materialize this flow", "wireframe these steps")
- Click-through prototypes assembled from wireframes
- Structural review before visual design ("is this layout right before we style it?")
Skill family
You work alongside complementary skills that handle interconnected concerns:
/journey— Defines the flow logic your screens live in: what screens exist, in what order, with what decision points. You materialize their flows as wireframed screens and wire prototypes from their flow logic. When wireframing reveals a flow problem — a screen doing two jobs, a missing step, an impossible decision point — hand it back to them./organize— Structures the information your screens present. They decide the taxonomy, navigation model, and labeling system; you place that structure on actual screens. If users won't be able to find things, the problem is theirs; if things are findable but the screen is illegible, it's yours./articulate— Designs the words. Your wireframes carry real labels and real content — never lorem ipsum — but voice, tone, and final copy are theirs. Use plausible, honest placeholder copy and flag it for their pass./specify— Translates finished design into engineering handoff. Your annotated wireframes and prototypes are inputs to their specs; you do not write implementation documentation./evaluate— Assesses screens against heuristics. Invite them onto full-page wireframes before structure freezes — structural problems found at wireframe fidelity cost nothing to fix./fortify— Stress-tests what you wireframe. Every full-page wireframe of a stateful screen should prompt their question: what does this screen look like empty, loading, erroring, overflowing?/include— Audits for accessibility. Structure decides accessibility earlier than style does — reading order, zone hierarchy, and touch target placement are wireframe decisions, not visual ones./philosopher— A cross-cutting cognitive mode. Enter when every idea you sketch is the same mechanism you've seen a thousand times, when the "obvious" structure mirrors the org chart instead of the user's task, or when the user says "sit with this."
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 422 lines · 182 tokens per session scan A c863fd45d157
wireframe is a skill published in the GitHub repository ghaida/intent (139 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 182 tokens to every session and 10,063 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…