webkit-navigation

A set of layout rules for choosing between two navigation shells in an Azion web console: one for browsing and one for focused create, edit, or deploy work.

In plain words
What is it for?
Use it when deciding or reviewing a page’s shell, header, sidebar, breadcrumbs, and signed-in user display.
Why use it?
It prevents pages from having the wrong navigation, which can either strand users or distract them from an unfinished task.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/aziontech/webkit/webkit-navigation
Any agent
npx skills add aziontech/webkit --skill webkit-navigation
Clone the repo
git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code, Codex.

Per session 217 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,143 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00217 $0.08143
Opus 5 $0.00109 $0.04071
Sonnet 5 $0.00043 $0.01629
Haiku 4.5 $0.00022 $0.00814

Measured yesterday against content hash bd4cf4efe96f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

webkit-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 yesterday.

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.

packages/webkit/cli-templates/claude/skills/webkit-navigation/SKILL.md · 631 lines

How it starts

The opening of the file, as written. The whole thing — 631 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: webkit-navigation

Purpose

Every screen in a console lives in one of two navigation shells, and picking the wrong one — or worse, blending them — is where a prototype stops feeling like one product. A browse page with no way back to the rest of the console strands the user; a focused create flow that keeps the full sidebar lets the user wander off mid-task and lose their work. This skill fixes which shell a page uses, how each is composed on @aziontech/webkit, and the one invariant they share: the signed-in user is always visible. It is the layout-shell companion to webkit-form (what goes inside a focused flow) and webkit-ux-heuristics (states + feedback).

How to use

  • /webkit-navigation Apply the shell rules below to any page or flow you build in this conversation.
  • /webkit-navigation <file> Review the file against the rules and output, per gap:
    • the exact line / element (quoted),
    • which rule it breaks (1 short sentence),
    • the concrete fix, naming the shell or webkit primitive to use.

When to invoke

  • Starting a new page and deciding how it sits in the app (a hub page vs a create/edit/deploy flow).
  • The user asks "which header goes here", "should this have a sidebar", "how do I get back", "the user disappeared on the create screen".
  • Reviewing a screen for whether it uses the right shell and shows exactly one header.

How to find the components

Never guess an import path, and never copy one from another repo or sample app — files move. Resolve every webkit primitive the same way:

  • Ask the webkit MCPsuggest_component in plain words ("sidebar", "app header", "breadcrumb").
  • Or read node_modules/@aziontech/webkit/catalog.json — every key under imports is a real published subpath. If a subpath is not a key there, it does not exist.

The primitives you compose the shells from — sidebar (+ sidebar-header, sidebar-group, sidebar-footer), global-header, breadcrumb, tab-view — all resolve this way. There is no @aziontech/webkit/app-layout and no @aziontech/webkit/creation-header: the two shells are components you compose in your own app (shown below), not webkit imports — never copy a dead import for them.

Read the full file on GitHub · 631 lines

Changes

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.

  1. yesterday First seen · 631 lines · 0 tokens per session scan A bd4cf4efe96f

Subscribe to this mod's changes

webkit-navigation is a skill published in the GitHub repository aziontech/webkit (2 stars, last pushed 4d ago), licensed MIT. It adds 217 tokens to every session and 8,143 once invoked, about $0.0011 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.

Related

Other skills, from other repositories

monorepo-management

Sets up or audits a monorepo workspace: tool selection, package naming, shared tooling, inter-package dependencies, selective CI, and versioning strategy. Invoked when the user asks to set up a monorepo, add a workspace, or manage multiple packages in a single repository.

soulcodex/agentic · 63 tokens

bazel-monorepo-expert

Expert knowledge for managing large-scale Bazel monorepos with multiple services, shared libraries, and cross-cutting concerns. Use for workspace structure, visibility, and dependency management.

kinhluan/rules-quarkus-skills · 43 tokens

pnpm

Skill "pnpm" from pledgeandgrow/pledge-skills, covering pnpm documentation skill, key benefits, file index, quick start and install pnpm.

pledgeandgrow/pledge-skills · 31 tokens

fast-typescript-check

Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…

internet-development/www-sacred · 84 tokens

port-sacred-terminal-ui-to-typescript-cli

Take a React Window.tsx (or any sacred component) and produce a terminal CLI screen written in TypeScript that uses Simulacrum — the sacred CLI framework in scripts/cli/lib/.

internet-development/www-sacred · 0 tokens

port-sacred-terminal-ui-to-react-using-same-conventions

Take a CLI screen written for Simulacrum — the sacred CLI framework (scripts/cli/templates/.ts or scripts/python/templates/.py) — and produce a React component that lives inside components/examples/ (or components/) using only sacred's existing primitives — Window, Card, SimpleTable, ActionButton, RowSpaceBetween…

internet-development/www-sacred · 0 tokens