Borrowing it
Nothing to install: this file belongs to MAIAS-project/maias. 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/MAIAS-project/maias/main/.claude/skills/maias-wireframe/SKILL.mdgit clone --depth 1 https://github.com/MAIAS-project/maiasWrote 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/maias-project/maias/maias-wireframe)<a href="https://agentmods.dev/skills/maias-project/maias/maias-wireframe"><img src="https://agentmods.dev/badge/skills/maias-project/maias/maias-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/maias-project/maias/maias-wireframe"><img src="https://agentmods.dev/badge/skills/maias-project/maias/maias-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.00076 | $0.01120 |
| Opus 5 | $0.00038 | $0.00560 |
| Sonnet 5 | $0.00015 | $0.00224 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
maias-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 10d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maias-wireframe
Turn a MAIAS document into mobile wireframes that look like phone screens, not page fragments. Default target is a standalone HTML file rendered by the toolchain; Figma and Miro when asked and their tools are available.
Ground rules
- The document is the source of truth.
./node_modules/.bin/maias validate <file>first — zero errors before drawing (offer maias-edit fixes otherwise). Never invent screens, elements, tabs, or back buttons the document doesn't declare, and never drop ones it does. - The HTML renderer is the toolchain's — never write one. Do not hand-author wireframe markup and do not write a generator script in any language:
maias wireframeis the single deterministic renderer, tested against the reference files in CI. (House rule: skills contain judgment and orchestration, never algorithms.) - Figma/Miro only: get structure from the toolchain, not by re-reading YAML —
maias tree <file> --jsongives the tab bar, flows, screen order, and per-screen markers (modal/auth/deep_link/back). Read both reference files before drawing:reference/chrome-layout.mdandreference/element-visuals.mdare the rendering specmaias wireframeimplements, and what you must reproduce in the design tool. - Generate the wireframes directly in the chosen target — do not screenshot the MAIAS Browser or point at a hosted viewer.
Target: HTML (default — zero prerequisites)
- Render:
./node_modules/.bin/maias wireframe <file> -o <app>-wireframes.html— one self-contained file (inline CSS, no JS, no CDN): one phone frame per screen, one row per flow, click-through anchors between frames. The command reportsN screens, M frames, F flows. - Map customisation requests to flags, not to hand edits:
- brand colour →
--accent <hex>(default is wireframe grey) - empty/loading/error state frames →
--states(off by default) - one flow only →
--flow <name> - render despite validation errors →
--force(dangling targets become dead links; prefer fixing the document)
- brand colour →
- Finish with
open <file>and tell the user what they're looking at: rows = flows, click links to follow navigation, relay the reported counts.
What ships with it
2 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.
- 10d ago First seen · 53 lines · 76 tokens per session scan A 1388f43445cc
maias-wireframe is a skill published in the GitHub repository MAIAS-project/maias (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 1,120 once invoked, about $0.0004 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-31.
Other skills, from other repositories
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.