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.
git 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/commands/navraj007in/architecture-cowork-plugin/user-journeys)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/user-journeys"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/user-journeys/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/commands/navraj007in/architecture-cowork-plugin/user-journeys"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/user-journeys.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.00013 | $0.01966 |
| Opus 5 | $0.00006 | $0.00983 |
| Sonnet 5 | $0.00003 | $0.00393 |
| Haiku 4.5 | $0.00001 | $0.00197 |
Grade A, and why
user-journeys 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 8d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:user-journeys
Trigger
/architect:user-journeys
Purpose
Map the complete user experience from discovery through retention. Produces detailed journey maps that reveal design opportunities, potential drop-off points, and emotional dynamics — directly informing UI/UX decisions, onboarding flows, and feature prioritization.
Workflow
Step 1: Gather Context
Read in this order:
architecture-output/_state.json— read first if it exists; useproject,personas,mvp_scope,market_researchdirectly — these replace reading intent.json and full markdown filesintent.json— only if_state.json.projectis absent; extract name, vision, core features- SDL — only if
_state.json.componentsis absent; checksolution.sdl.yamlfirst; if absent, readsdl/README.mdthen the relevant module files. Grep forproduct:block (screens, coreFlows) andcomponents:block only — do NOT read the full file architecture-output/user-personas.md— only if_state.json.personasis absent; if reading, Grep for persona goals and "Current workflow" sections onlyarchitecture-output/mvp-scope.md— only if_state.json.mvp_scopeis absent; if reading, Grep for "Must Have" section onlyarchitecture-output/deep-research.md— only if_state.json.market_researchis absent; if reading, Grep for competitor weakness/UX gaps only
Step 2: Identify Core Journeys
Define 4-6 journeys covering the full lifecycle:
- Discovery → Signup — how each persona finds and evaluates the product
- Onboarding → First Value — from signup to the "aha moment"
- Core Loop — the primary repeated action that delivers ongoing value
- [Feature-Specific Journey] — for 1-2 key features from MVP scope
- Error/Recovery — what happens when things go wrong
- Upgrade/Expansion — from free to paid, or from basic to advanced usage
Step 3: Generate Each Journey Map
For EACH journey, produce ALL of the following:
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.
- 8d ago First seen · 197 lines · 13 tokens per session scan A dadd1075aab4
user-journeys is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,966 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 commands, from other repositories
verify
Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
theme
Switch between visual theme skins — OLED Black, Matrix, Claude Anthropic, Surprise Me.
stark-director
Use this command when the user asks Stark to go all out, raise design quality broadly, use libraries well, make a UI feel actually designed, or coordinate research, typography, motion, usability, implementation, and QA in one pass.
data-visualization-specialist
Use when a chart misleads or confuses. Wrong chart type for the data, a truncated axis, colour that encodes nothing, unreadable labels on mobile, or charts no screen reader can use.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.