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 Uxcel-Lab/product-skills --skill navigationgit clone --depth 1 https://github.com/Uxcel-Lab/product-skillsWrote 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/uxcel-lab/product-skills/navigation)<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/navigation"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/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/skills/uxcel-lab/product-skills/navigation"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/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.00089 | $0.02930 |
| Opus 5 | $0.00044 | $0.01465 |
| Sonnet 5 | $0.00018 | $0.00586 |
| Haiku 4.5 | $0.00009 | $0.00293 |
Grade A, and why
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 11d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigation Skill
How this skill behaves (read first)
This is a generative skill. The default failure modes: pattern-by-habit (a top bar with a hamburger regardless of IA depth, breadth, or platform), hidden essentials (core sections buried behind icons), and missing wayfinding (no "you are here" signals, so users dropped in by search are lost). Navigation is chosen by the structure of the content and how users move through it — not by what modern sites look like. This skill gates:
- Establish the IA shape and platform — these mostly decide the pattern.
- Apply the always-true core — system layering, wayfinding signals, visible essentials, interaction basics.
- Surface the pattern decisions (top bar vs. sidebar, hamburger, mega menu, tabs, breadcrumbs, pagination vs. infinite scroll) with trade-offs.
Then it hands off to ux-heuristics-audit, ux-accessibility-audit, ux-aesthetics-audit, and ux-microcopy-audit — and, as a multi-screen structure, to ux-information-architecture-audit.
Step 0 — Establish context before designing
Ask if not known; state the assumption if proceeding without an answer:
- IA shape — how many top-level sections, how deep the hierarchy, and is it expected to grow? (Breadth/growth pushes toward vertical nav and mega menus; shallow + stable fits a top bar or tabs.)
- Platform — desktop, mobile, or responsive? Mobile flips defaults: bottom nav for top destinations, single-breadcrumb, hamburger placement by OS convention.
- Content-focused or task-based? Content apps (news, video) can minimize chrome and hide secondary nav; task apps (booking, fitness) need persistent, visible navigation.
- Entry points — do users land deep via search/links? Then wayfinding signals (breadcrumbs, titles, URLs) matter far more than the homepage path.
The always-apply core (correct for almost every case)
Layer the navigation systems — each has a job
Global (main sections, consistent on every page) · local (within a section; inverted-L with global on top) · contextual (related links in/after content) · utility (login, search, language, account — top corner, familiar labels, text language names not flags) · footer (legal, sitemap, contact, social; a "fat footer" can carry rich secondary nav). Don't make one layer do another's job — breadcrumbs never replace global nav.
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.
- 11d ago First seen · 144 lines · 89 tokens per session scan A 9f29947a1885
ux-navigation is a skill published in the GitHub repository Uxcel-Lab/product-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 2,930 once invoked, about $0.0004 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 skills, from other repositories
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
interface-polish
Design-engineering micro-detail pass for interfaces that already work but feel unrefined. Applies concrete CSS/JS rules for hover/active/focus states, transition timing and easing, enter/exit animations, stagger patterns, layered shadows, border-vs-shadow elevation, nested border-radius, optical alignment, typography…
premium-hero-builder
Build premium, dark-themed hero sections and landing pages with cinematic video backgrounds, liquid glass morphism, editorial typography, and pixel-perfect specifications. Based on the Viktor Oddy methodology of detailed design prompts that produce agency-quality results from AI code generation. Use when building hero…
page-flow-cleanup-audit
A review process for cleaning up a user-facing page or feature flow by tracing where its data and states come from. It checks loading, empty, error, permission, and lifecycle behavior before removing unnecessary code.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…
empty-states
Turn dead ends into moments that build trust and guide action. Covers zero-data screens, error recovery, loading states, and retention micro-copy. Use when handling empty dashboards, failed searches, or moments where users hit a wall.