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/jonase47/ccprWrote 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/jonase47/ccpr/p3-ux-navigation)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-ux-navigation"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-ux-navigation/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/jonase47/ccpr/p3-ux-navigation"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-ux-navigation.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.00000 | $0.00868 |
| Opus 5.5 | $0.00000 | $0.00347 |
| Sonnet 5.5 | $0.00000 | $0.00174 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
p3-ux-navigation 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-ux-navigation – Sitemap & Information Architecture
Creates the navigation structure, sitemap and identifies critical flows.
Argument: $ARGUMENTS = [Focus, e.g. "Onboarding", "Dashboard", "Mobile"]
If provided: Focus the navigation analysis on the named area. If not provided: Create complete sitemap for the MVP scope.
Prerequisites
- USER_JOURNEYS.md and FEATURES.md exist
Agent
- Type: ux-designer
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From USER_JOURNEYS.md: Personas and journeys (short version)
- From FEATURES.md: Must-Have features with screens
- From ARCHITECTURE.md: Technical constraints for navigation (if relevant)
Prompt Template
Goal: Create sitemap and navigation structure. Focus: $ARGUMENTS
Context: [inline from USER_JOURNEYS.md, FEATURES.md]
Output Format:
- Sitemap as ASCII tree (hierarchy of screens)
- Navigation pattern: Tab Bar / Sidebar / Breadcrumb – with justification
- Critical flows: Table | Flow | Steps | Friction Points |
Constraints:
- ONLY navigation and information architecture
- NO wireframes, NO dark mode, NO accessibility
- Max. 15 screens in the sitemap
- Max. 5 critical flows
Orchestrator Checkpoint
- All must-have features have at least one screen?
- Critical flows cover the most important user journeys?
Write Detail File
Write the result to docs/architecture/NAVIGATION.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: ux-navigation
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Sitemap (ASCII tree), ## Navigation Pattern (with justification), ## Critical Flows (the table flow / steps / friction points).
Update Sub-Index
Update docs/architecture/UX_CONCEPT.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[NAVIGATION.md](NAVIGATION.md)with statuscomplete. - Lift the navigation pattern decision into Key Decisions of the sub-index (e.g.
- Bottom tab bar with 4 tabs → see NAVIGATION.md). - Do not edit
ARCHITECTURE.mddirectly.
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.
- 1mo ago Changed f2e9712e012d
- 1mo ago First seen · 87 lines · 0 tokens per session scan A 1fe3ab5170d7
p3-ux-navigation is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 868 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.
Other commands, from other repositories
design-intent
Guided UI/visual development with structured exploration, architecture design, and quality review.
prompt
Generate Google Stitch-ready prompts from briefs or spec files using the authoring skill.
stitch-generate
Full Stitch pipeline — author prompts, generate screens via MCP, fetch images and code.
prototype
Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery.
stitch-setup
Guided setup and verification of Stitch MCP server connection.
ccc-theme
List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.