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 JiuNian3219/architext --skill archi-ui-wireframegit clone --depth 1 https://github.com/JiuNian3219/architextWrote 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/jiunian3219/architext/archi-ui-wireframe)<a href="https://agentmods.dev/skills/jiunian3219/architext/archi-ui-wireframe"><img src="https://agentmods.dev/badge/skills/jiunian3219/architext/archi-ui-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/jiunian3219/architext/archi-ui-wireframe"><img src="https://agentmods.dev/badge/skills/jiunian3219/architext/archi-ui-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.00027 | $0.01740 |
| Opus 5 | $0.00014 | $0.00870 |
| Sonnet 5 | $0.00005 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
archi-ui-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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invocation
- Auto-invoke: No, not triggered by model based on description.
- Trigger location: Only explicitly called by
/archi.uior plan/change's UI local update step. - Execution context: Can execute via Skill tool or current context; must follow calling protocol's Gate before writing
screens/. - Boundary: Only generate UI concept drafts and reference files, does not generate production source code.
UI Concept Design
Core Principles
- Interactive display: Draw buttons / forms / modals and bind clicks, clicks only trigger visual feedback (state switch / panel expand / modal show/hide), not real business logic
- Content fill: Use real business names from roadmap; No "Title", "[Button]" placeholders; Lists / tables ≥ 3-4 rows of realistic dummy data; Empty states write specific copy not "No data"
- Palette discipline: Only use CSS variables derived from
design_tokens.json, no hardcoded magic numbers - Output boundary:
screens/is concept design and acceptance reference, not production code; Must not instruct subsequent implementation to directly copy HTML/CSS/JS, must require rewrite using project's own language, framework and style system - No anti-patterns: Purple gradient / emoji / non-pure black-white [[INCLUDE: shared/ui-redlines.md]]
Step 1 — Read Context
Extract from context_files:
- vision.md → Platform / Users / North star
- roadmap.json → UI tasks → Screen mapping
- design_tokens.json → Aesthetic / Brand color / Decor variables
- tech_stack.md → Platform / Navigation framework
- Current
ui_context.md→ Existing screen IDs and names (adopt/incrementalreuse)
adopt mode additionally: Extract from adopt_codebase "Route → Screen list", "Layout components → Navigation structure", "Page components → Core regions and states".
Step 2 — Plan Screen List
Assign screen IDs (S-01, S-02 ..., permanent) mapping to Roadmap tasks. incremental only processes scope_screens.
| Screen ID | Screen Name | Corresponding Task | Status List |
|---|---|---|---|
| S-01 | default, loading, empty, error |
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 · 152 lines · 27 tokens per session scan A 264bf666171e
archi-ui-wireframe is a skill published in the GitHub repository JiuNian3219/architext (14 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 1,740 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-08-30.
Other skills, from other repositories
ppt-orchestrator
A dispatcher for creating presentations, slide decks, long images, and weekly reports. It chooses a visual style and output format, then sends the work to a more specialised add-on.
zhongguose-html-skill
An HTML-only presentation system using traditional Chinese colours and Chinese-style visual design. It helps organise source material into a report structure and produces a self-contained HTML file with its assets.
omh-frontend
This is a Hermes-native frontend workflow skill.
omh-visual-qa
This is a Hermes-native visual-qa workflow skill.
omh-accessibility-audit
This is a Hermes-native accessibility-audit workflow skill.
omh-design-orchestration
This is a Hermes-native design-orchestration workflow skill.