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 AlpacaLabsLLC/skills-for-architects --skill normagit clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architectsWrote 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/alpacalabsllc/skills-for-architects/norma)<a href="https://agentmods.dev/skills/alpacalabsllc/skills-for-architects/norma"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/norma/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/alpacalabsllc/skills-for-architects/norma"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/norma.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.00045 | $0.01070 |
| Opus 5.5 | $0.00018 | $0.00428 |
| Sonnet 5.5 | $0.00009 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
norma 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 1mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
norma
Before acting, read the host contract and this component’s declaration (skill:norma). Load only applicable modes from the shared catalog; declarations do not grant access or permission. Use the actual host’s delivery route.
Norma coordinates architecture, building, project, client and firm work inside the user's existing harness. It is a role, not an independent runtime or service. Keep direct specialized skill requests with their owner. For coordination use the current component registry and relevant descriptions; do not load a fixed keyword routing table or require a Norma hop before every skill.
For Arch Studio onboarding, installation, access, memory or troubleshooting questions, select Norma support. It shares support knowledge across channels but grants no email/case access. General architectural coordination remains here; do not treat all Norma work as support-only activity.
Scope and state
Infer the intended outcome and preserve the requested extent. Select the narrowest appropriate owner and continue necessary dependencies under existing authorization. Use moments only when relevant to actual state. A question or one-off artifact stays standalone. Resolve studio/project context only for durable work or needed project records; do not treat missing studio as invalidating a valid standalone project. A declined setup offer does not recur as a gate.
For source-directory questions, use the source catalog as metadata only: filter geography/topic, deduplicate, return original links and explain coverage. NYC code routes are distinct from related data routes and shared/state sources. Unregistered LA coverage is a gap, not permission to substitute NYC. Substantive interpretation retrieves the applicable original through the owning skill.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 46 lines · 45 tokens per session scan A a95d943d9088
norma is a skill published in the GitHub repository AlpacaLabsLLC/skills-for-architects (385 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,070 once invoked, about $0.0002 per session on Opus 5.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-09-21.
Other skills, from other repositories
cre-development
CRE Development and Construction suite - 8 specialist skills for U.S. site/entitlement screening, budget and yield-on-cost, construction loan sizing, GC contracts, draw review, schedule risk, lease-up pro forma, and IC memo writing.
technical-roadmap-planning
Gathers inputs, defines initiatives, prioritises with an impact/effort matrix, sequences dependencies, and produces a roadmap table. Invoked when the user asks to plan a technical roadmap, prioritise engineering initiatives, or create a quarter/half-year engineering plan.
github-issue-planning
Issue-backed plan persistence on GitHub via one managed issue comment with an idempotent marker. Prefers GitHub MCP when available and falls back to gh CLI when MCP is unavailable or misconfigured. Uses local plan persistence only when issue persistence is unavailable or not desired.
module-federation-ssr
Add, review, or debug server-side rendered Module Federation applications, including Modern.js, Nuxt, Next.js legacy Pages Router, Vinext, Vite SSR, and dual browser/server remote artifacts.
sparc-pipeline
Use when you need to run the full 5-phase SPARC methodology (Specification→Pseudocode→Architecture→Refinement→Completion) for a complex feature. Each phase has explicit done-criteria gates.
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.