p3-ux-wireframes

Install

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.

agentmods

npx agentmods add commands/jonase47/ccpr/p3-ux-wireframes

Clone the repo

git clone --depth 1 https://github.com/jonase47/ccpr

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jonase47/ccpr/p3-ux-wireframes.svg)](https://agentmods.dev/commands/jonase47/ccpr/p3-ux-wireframes)

Your own site

<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-ux-wireframes"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-ux-wireframes.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,337 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown No closer match found in the catalogue.

Token cost

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	$0.00000	$0.01337
Opus 5	$0.00000	$0.00668
Sonnet 5	$0.00000	$0.00267
Haiku 4.5	$0.00000	$0.00134

Measured today against content hash a042d800b737, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

p3-ux-wireframes 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 today.

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.

commands/p3-ux-wireframes.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/p3-ux-wireframes – Wireframes for Key Screens

Creates wireframes (ASCII art) for the most important screens with interaction descriptions.

Argument: $ARGUMENTS = [Screen name, e.g. "Start Page", "Core Screen", "Error State"]

If provided: Create wireframe for the named screen. If not provided: Create wireframes for all key screens.

Prerequisites

Sitemap from /p3-ux-navigation available

Agent

Type: ux-designer
Model: sonnet

Context (Orchestrator prepares)

Orchestrator reads beforehand and delivers inline:

From UX_CONCEPT.md: Sitemap and critical flows
From FEATURES.md: Feature details for the affected screens
From USER_JOURNEYS.md: Relevant persona and journey

Prompt Template

Goal: Create wireframes for: $ARGUMENTS

Context: [inline from UX_CONCEPT.md, FEATURES.md]

Output Format: Per screen:

ASCII art wireframe (approx. 20-30 lines)

Element description: Table | Element | Type | Interaction |

UX decision (1 sentence why this layout)

Required screens: Start Page, Core Screen, Empty State, Error State

Constraints:

ONLY wireframes and interaction descriptions

NO color specifications, NO dark mode

Max. 5 screens per call

ASCII art must be readable in monospace

Orchestrator Checkpoint

All required screens covered (or skipped with justification)?
Every element has an interaction description?

Write Detail Files

The result can be written flat (single WIREFRAMES.md) or as sub-index with per-screen detail files, depending on size. ASCII wireframes are large per screen; once you have several screens, the flat layout blows past read-budgets.

Choose Layout

Condition	Layout
≤5 screens AND result fits in <25 KB	Flat: single `WIREFRAMES.md`
≥6 screens OR result ≥25 KB	Sub-Index: lean `WIREFRAMES.md` + `wireframes/` subfolder with one detail file per screen

Flat Layout (small wireframe sets)

Write docs/architecture/WIREFRAMES.md (overwrite if it exists). Frontmatter:

Read the full file on GitHub · 139 lines

Changes

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.

today First seen · 139 lines · 0 tokens per session scan A a042d800b737

Subscribe to this mod's changes

p3-ux-wireframes is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,337 tokens. 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.

Design and UX Frontend agentic-workflows ai-agents anthropic claude claude-code claude-code-agents