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 rules/ghaida/intent/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.00179 | $0.26804 |
| Opus 5 | $0.00089 | $0.13402 |
| Sonnet 5 | $0.00036 | $0.05361 |
| Haiku 4.5 | $0.00018 | $0.02680 |
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 — 1,576 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 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 · 1,576 lines · 26,804 tokens per session scan A 449e7207170b
wireframe is a cursor rule published in the GitHub repository ghaida/intent (139 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 179 tokens to every session and 26,804 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.