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 commands/rajconnects/founder-stack/ux-wireframegit clone --depth 1 https://github.com/rajconnects/founder-stackWhat 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.00059 | $0.00687 |
| Opus 5 | $0.00030 | $0.00344 |
| Sonnet 5 | $0.00012 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
ux-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 yesterday.
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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the wireframe step of the UX design layer.
Arguments: $ARGUMENTS
Steps
-
Resolve scope. Parse
$ARGUMENTS. If empty orauto, readspec_roots.frontendthenspec_roots.build_plansfrom.claude/project.jsonand pick the most recently modified spec file under those roots. Otherwise use the path/scope given. If no spec resolves, fail loudly:ux-wireframe requires a spec path or scope. Try /ux-wireframe auto if a recent frontend spec exists. -
Compute the scope slug. Slugify the scope label (or the spec's primary component name) for marker filenames: lowercase, alphanumerics + dashes only.
-
Resolve config and inline. Read
.claude/project.jsononce. Extract:spec_roots,design_system.components_spec,design_system.flow_spec,design_system.tokens,design_system.principles(may be null),design_system.figma.file_key,design_system.figma.screens,stack.frontend,stack.frontend_root. Ifstack.frontendis null, fail:ux-wireframe only runs for frontend specs (stack.frontend is null).Ifcomponents_specorflow_specis null, fail:ux-wireframe requires components_spec and flow_spec paths. -
Launch
ux-wireframerwith a self-contained prompt containing: the resolved spec path, scope label and slug, the inlined config fields above, the--sourcereference (if any), and the--skip-when-trivialflag (if any). Do NOT ask the agent to re-readproject.json. -
Print the agent output verbatim. Do not soften or reinterpret. The agent's output is the wireframe deliverable.
-
Mark on success. If verdict is
ARTIFACTS_PRODUCED,touch .claude/.ux-wireframe-passed-<scope-slug>. OnERROR, do not write the marker. -
Closing line. On success print:
wireframe ready: review the [WIREFRAME] frames in Figma, then run /ux-mockup <scope>.
Notes
--skip-when-trivialis for one-line scopes that don't warrant Figma frames. The agent still extendscomponents_spec/flow_specand writes the marker.- The marker is gitignored and per-session.
.claude/.ux-wireframe-passed-<scope-slug>is consumed by/ux-mockupas a hard prerequisite. - If
design_system.figma.file_keyis null, the agent skips Figma writes entirely and still produces the spec extensions.
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.
- yesterday First seen · 31 lines · 59 tokens per session scan A e4d587e7abd9
ux-wireframe is a command published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 687 once invoked, about $0.0003 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.