Borrowing it
Nothing to install: this file belongs to extra-org/extra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/extra-org/extra/main/.claude/skills/project-architecture/SKILL.mdgit clone --depth 1 https://github.com/extra-org/extraWrote 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/extra-org/extra/project-architecture)<a href="https://agentmods.dev/skills/extra-org/extra/project-architecture"><img src="https://agentmods.dev/badge/skills/extra-org/extra/project-architecture/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/extra-org/extra/project-architecture"><img src="https://agentmods.dev/badge/skills/extra-org/extra/project-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00547 |
| Opus 5.5 | $0.00013 | $0.00219 |
| Sonnet 5.5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
project-architecture 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 2mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Project Architecture
When to use this skill
Always. Read this before any change, regardless of area. It anchors every other skill in the project's non-negotiable rules and layout.
Files to read first
AGENTS.mddocs/ARCHITECTURE.mddocs/ROADMAP.mddocs/adr/
Architecture rules
- The pipeline is one-directional:
config.yml → validate → compile → CompiledAgentGraph → RuntimeEngine → ExecutionContext (per request) → execution → response + trace. - YAML is declarative specification, never executable business logic.
- Validate before compile; compile before run. The runtime sees only compiled, typed models — never raw YAML dicts.
RuntimeEngineis created once at startup;ExecutionContextis per request.- Client-specific auth/business logic lives in customer plugins, not the runtime.
- Prompts are templates rendered per request; security is enforced at the tool/data layer, not via prompt text.
- Secrets never live in YAML or prompts.
Implementation rules
- Follow the planned package layout in
AGENTS.md(src/agentplatform/<layer>). No giant single-file modules. - Keep each module to one architectural responsibility.
- Respect layer boundaries: a layer depends only on the typed outputs of the layers before it.
- Do not change public contracts (YAML schema, plugin contracts, API shape) without an ADR and approval.
- Stay within the current task's scope; propose new tasks for discovered work.
Validation checklist
- Change fits the layered architecture and the planned layout.
- No architecture rule from
AGENTS.md§3 is violated. - No contract changed without an ADR.
- Tests added for new behavior.
-
make checkpasses.
Common mistakes to avoid
- Reading raw YAML in the runtime instead of compiled models.
- Adding request state to
RuntimeEngineor the compiled graph. - Putting customer auth/business logic in the runtime.
- Expanding scope beyond the current task or doing large uncontrolled rewrites.
- Relying on prompt wording for security.
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.
- 2mo ago First seen · 68 lines · 32 tokens per session scan A 6b137c8dce90
project-architecture is a skill published in the GitHub repository extra-org/extra (117 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 547 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
skill-writing-plans
Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning.
argent-tv-interact
Control and inspect TV apps via argent, Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
agenticx-query-data-source
Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
06-product-brief
Produces a concise Product Brief before requirements. Use when the user wants to frame or revisit a product opportunity and how it will be validated. Not for requirements, technical design, or planning.
issue-resolve
Use when an assessed gflow-cli issue (verdict CONFIRMED-BUG or LIKELY-BUG) has localized, verifiable scope and should be driven to a fix. Mutating and gated: it works in an isolated worktree, fixes test-first, and opens a DRAFT PR for human review. Built to run autonomously (hermes-ops) within a strict action envelope…