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 Owl-Listener/inclusive-design-skills --skill wayfinding-navigationgit clone --depth 1 https://github.com/Owl-Listener/inclusive-design-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/owl-listener/inclusive-design-skills/wayfinding-navigation)<a href="https://agentmods.dev/skills/owl-listener/inclusive-design-skills/wayfinding-navigation"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/wayfinding-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/owl-listener/inclusive-design-skills/wayfinding-navigation"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/wayfinding-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.00082 | $0.00541 |
| Opus 5 | $0.00041 | $0.00270 |
| Sonnet 5 | $0.00016 | $0.00108 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
wayfinding-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 12d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wayfinding and Navigation
Design navigation so that people with cognitive and memory difficulties can find content, understand where they are, and get back to where they were — without relying on memory.
Core Principle
Users should always be able to answer three questions instantly:
- Where am I?
- Where can I go?
- How do I get back?
If any answer requires more than 1 second of thought, the navigation has failed.
Design Patterns
Signpost Pattern
- Breadcrumbs in hierarchies deeper than 2 levels
- Step indicators in multi-step flows ("Step 2 of 4")
- Active section highlighted in navigation
- Page titles that match the link that brought the user here
Minimal Path Pattern
- Important actions reachable in 1–2 clicks from any screen
- Breadth over depth — flatten deep hierarchies
- Shortcuts to frequently used content
- "Back to [last meaningful location]" always available
Multiple Routes Pattern
- Search AND browse AND shortcuts for all important content
- Don't force a single path to any destination
- "Jump to" links for long pages
- Recently visited and frequently used sections accessible
Chunking Pattern
- Break long content into headed sections (3–5 paragraphs each max)
- Table of contents for pages longer than 3 screens
- Progressive disclosure for detail
- Group related form fields into labelled fieldsets
Assessment Checklist
- Every page has a clear, descriptive title
- Navigation is consistent across all pages (same position, same order)
- Current location is always visually indicated
- Breadcrumbs or back links are present in hierarchies
- Multi-step flows show progress and allow backward movement
- Search is available on every page
- Important actions are reachable in 2 clicks or fewer
- Headings describe content (not just categories)
- Link text describes the destination (no "click here")
Output Format
When reviewing: identify navigation failures with specific locations and recommended fixes. When designing: present the information architecture with cognitive accessibility annotations.
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.
- 12d ago First seen · 65 lines · 82 tokens per session scan A a58fb1848723
wayfinding-navigation is a skill published in the GitHub repository Owl-Listener/inclusive-design-skills (98 stars, last pushed 3mo ago), licensed MIT. It adds 82 tokens to every session and 541 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-30.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…