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 dazz/kostja94-marketing-skills --skill navigation-menugit clone --depth 1 https://github.com/dazz/kostja94-marketing-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/dazz/kostja94-marketing-skills/navigation-menu)<a href="https://agentmods.dev/skills/dazz/kostja94-marketing-skills/navigation-menu"><img src="https://agentmods.dev/badge/skills/dazz/kostja94-marketing-skills/navigation-menu/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/dazz/kostja94-marketing-skills/navigation-menu"><img src="https://agentmods.dev/badge/skills/dazz/kostja94-marketing-skills/navigation-menu.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.00076 | $0.00861 |
| Opus 5 | $0.00038 | $0.00430 |
| Sonnet 5 | $0.00015 | $0.00172 |
| Haiku 4.5 | $0.00008 | $0.00086 |
Grade A, and why
navigation-menu-generator 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.
This is a copy
100% identical to navigation-menu-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Components: Navigation Menu
Guides navigation menu design for SEO, UX, and accessibility. Navigation helps users find content and signals site structure to search engines.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for key pages and audience.
Identify:
- Site structure: Main sections, hierarchy
- Primary goals: Conversion paths, key pages
- Platform: Web, mobile, both
Structure & Organization
Menu Size
- Primary nav: 7-9 items; avoid overwhelming users
- Sub-navigation: Up to 2 levels; deeper topics in sub-menus
- Pattern: Horizontal top nav or vertical side nav; avoid novel patterns
Hierarchy
- Reflect sitemap structure; need not match exactly
- Prioritize what visitors need most
- Logical grouping by topic or task
SEO Best Practices
| Practice | Purpose |
|---|---|
| Semantic HTML | <nav>, <ul>, <li>; proper landmark roles |
| Descriptive anchor text | Target keywords; avoid "Click here" |
| Text links | Prefer text over images; crawlers need readable links |
| Initial render | All nav HTML in first paint; no JS-only menus for critical links. See rendering-strategies |
| Visible links | Prefer visible over hidden; helps crawlers understand structure |
Crawlability
- Sub-menus: Ensure HTML is in DOM (e.g., CSS-hidden, not JS-injected)
- Footer nav: Include secondary links
- Breadcrumbs: See breadcrumb-generator for implementation
UX Guidelines
Visibility & Location
- Desktop: Visible nav; avoid hiding behind hamburger when space allows
- Expected placement: Primary nav in header; footer nav at bottom
- Current location: Indicate active page/section in menu
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 · 96 lines · 76 tokens per session scan A 3bc0107c5cef
navigation-menu-generator is a skill published in the GitHub repository dazz/kostja94-marketing-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 861 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to navigation-menu-generator, differing in 0 lines, and is treated as a copy.
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.
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…
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.