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 navraj007in/architecture-cowork-plugin --skill wireframe-patternsgit clone --depth 1 https://github.com/navraj007in/architecture-cowork-pluginWrote 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/navraj007in/architecture-cowork-plugin/wireframe-patterns)<a href="https://agentmods.dev/skills/navraj007in/architecture-cowork-plugin/wireframe-patterns"><img src="https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/wireframe-patterns/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/navraj007in/architecture-cowork-plugin/wireframe-patterns"><img src="https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/wireframe-patterns.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.00023 | $0.01760 |
| Opus 5 | $0.00012 | $0.00880 |
| Sonnet 5 | $0.00005 | $0.00352 |
| Haiku 4.5 | $0.00002 | $0.00176 |
Grade A, and why
wireframe-patterns 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 7d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wireframe Patterns (JSON)
SDL → Screen Inventory
| SDL source | Screens |
|---|---|
auth section |
login, register, forgot-password |
product.screens |
use as-is (takes priority over inference) |
product.coreFlows |
one screen per distinct flow step |
data entity |
{entity}-list, {entity}-detail, {entity}-form |
| always | dashboard, settings-profile |
| subscriptions/billing | settings-billing |
| multi-tenant | settings-team |
| marketing/landing component | landing |
Section Types
| Type | Use for | Key fields |
|---|---|---|
header |
Page title + action buttons — use as FIRST section on every non-auth screen | title, subtitle?, actions? (array), badge? |
stats |
Metric cards with trends | items: [{label, value, trend?}] |
table |
Data lists with rows | title?, columns, rows |
form |
Input forms | title?, fields: [{label, type, options?}], submitLabel? |
detail |
Key-value pairs for a record | title?, pairs: [{label, value}] |
hero |
Landing page hero | headline, subheading?, cta? |
cards |
Feature/content cards | title?, cards: [{title, description?, badge?}] |
feed |
Activity/notification feed | title?, feed: [{user, action, time}] |
chat |
Messaging UI | channels, messages: [{user, time, text}] |
tabs |
Tabbed content sections | title?, tabs: [string] |
empty |
Empty state with CTA | title?, message?, action? |
Form field types: text, email, password, select (needs options), textarea, checkbox, toggle
Screen Patterns
login / register / forgot-password → layout: centered
{ "type": "form", "fields": [{"label":"Email","type":"email"},{"label":"Password","type":"password"}], "submitLabel": "Sign In" }
dashboard → layout: sidebar
{ "type": "header", "title": "Dashboard", "subtitle": "Welcome back", "actions": ["New Report"] },
{ "type": "stats", "items": [{"label":"Total Users","value":"1,240","trend":"+8%"},{"label":"Revenue","value":"$42K","trend":"+12%"},{"label":"Active Now","value":"38","trend":"+3%"},{"label":"Churn Rate","value":"2.1%","trend":"-0.4%"}] },
{ "type": "feed", "title": "Recent Activity", "feed": [{"user":"Alice Chen","action":"created a new order #1042","time":"2 min ago"},{"user":"James Liu","action":"updated billing details","time":"15 min ago"}] }
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.
- 7d ago First seen · 118 lines · 23 tokens per session scan A 527cadae3508
wireframe-patterns is a skill published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,760 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
river-review-architecture
An architecture-review guide that checks whether software design decisions, system boundaries, and data models fit together consistently. An architecture review examines the structure and dependencies of a system.
cognitive-interface-audit
Comprehensive cognitive interface audit with two modes and a single tier. Planning mode designs task models, user expertise mapping, and error tolerance strategy. Audit mode evaluates mental model alignment (Norman's Gulfs), consistency (Gestalt), error tolerance (Wood 7-layer defense), cognitive load (NASA-TLX…
Architecture Boundaries & Dependencies
Ensure architecture/design docs define clear boundaries, ownership, dependency direction, and change impact to avoid tight coupling.
Architecture Diagrams Readiness
Ensure architecture diagrams are readable, consistent with text, and clear on scope, boundaries, and data flow.
Architecture Traceability & Consistency
Ensure design changes stay consistent across ADRs, diagrams, and specs; decisions are traceable; and drift is explicitly managed.
uiux
Use when deciding how the product's UI should look and how its UX should behave, from the mockup and logic docs - visual direction, design system, and per-screen design chapters via an interview, using capstone's own vendored design method.