angular-multi-layout

A review skill for Angular applications with more than one page layout, such as a top navigation layout and a sidebar layout.

In plain words
What is it for?
Use it to check for a shared layout component, a layout-selection service, saved layout preferences, responsive sidebar collapse, and one navigation model.
Why use it?
It identifies duplicated layout code, scattered layout decisions, lost user preferences, missing mobile sidebar behavior, and repeated navigation data.

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/agenticpawan/fullstack-pilot/angular-multi-layout
Any agent
npx skills add AgenticPawan/FullStack-Pilot --skill angular-multi-layout
Clone the repo
git clone --depth 1 https://github.com/AgenticPawan/FullStack-Pilot

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,849 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.00057 $0.02849
Opus 5 $0.00028 $0.01425
Sonnet 5 $0.00011 $0.00570
Haiku 4.5 $0.00006 $0.00285

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

Security

Grade A, and why

angular-multi-layout 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.

plugins/pilot-angular/skills/angular-multi-layout/SKILL.md · 338 lines

How it starts

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

Standard IDs

ID Severity What it checks
AML-001 P1 Layout markup duplicated per page/route instead of one configurable shell component
AML-002 P1 No layout-selection abstraction (LayoutService) — layout branching scattered in templates
AML-003 P2 Layout preference not persisted — resets on reload
AML-004 P1 Sidebar layout has no responsive/mobile collapse to an overlay/drawer
AML-005 P2 Navigation menu data duplicated separately for header and sidebar variants

Check A — Centralized shell component (AML-001)

Detection

  1. Glob src/**/*.component.html for repeated structural blocks containing both a <nav>/ header-style menu markup and a <router-outlet> or page-content wrapper appearing in more than one top-level page component.
  2. Confirm a single shell exists: look for one component (commonly app-shell, layout-shell, or app.component.html itself) that contains the <router-outlet> all routed pages render into, with header/sidebar markup defined exactly once.
  3. Flag any top-level routed component that re-implements its own <header>/<nav> markup instead of relying on the shell wrapping it.

BAD — every page re-implements its own header/nav

<!-- dashboard.component.html -->
<header class="topbar">
  <nav><a routerLink="/dashboard">Dashboard</a><a routerLink="/orders">Orders</a></nav>
</header>
<main><h1>Dashboard</h1></main>
<!-- orders.component.html — duplicated header/nav -->
<header class="topbar">
  <nav><a routerLink="/dashboard">Dashboard</a><a routerLink="/orders">Orders</a></nav>
</header>
<main><h1>Orders</h1></main>

GOOD — one shell component, pages render inside its router-outlet

// app.routes.ts
export const routes: Routes = [
  {
    path: '',
    component: ShellComponent,
    children: [
      { path: 'dashboard', loadComponent: () => import('./dashboard.component').then(m => m.DashboardComponent) },
      { path: 'orders', loadComponent: () => import('./orders.component').then(m => m.OrdersComponent) }
    ]
  }
];
<!-- shell.component.html -->
@if (layout.mode() === 'header') {
  <app-header-layout><router-outlet /></app-header-layout>
} @else {
  <app-sidebar-layout><router-outlet /></app-sidebar-layout>
}
<!-- dashboard.component.html — content only, no header/nav markup -->
<h1>Dashboard</h1>

Read the full file on GitHub · 338 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 · 338 lines · 57 tokens per session scan A 641196f31143

Subscribe to this mod's changes

angular-multi-layout is a skill published in the GitHub repository AgenticPawan/FullStack-Pilot (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 2,849 once invoked, about $0.0003 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

azure-mgmt-apicenter-dotnet

Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API…

microsoft/skills · 97 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

azure-communication-chat-java

Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.

microsoft/skills · 41 tokens

union-type-wrappers

Add typed getters and setters over BinaryData properties that represent TypeSpec union types in generated Java models. Use when generated classes expose BinaryData for union-typed fields and you need ergonomic, type-safe accessors instead.

Azure/azure-sdk-for-java · 49 tokens

refresh-arm-sdk-release

WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…

Azure/azure-sdk-for-net · 91 tokens

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…

Azure/azure-sdk-for-net · 192 tokens