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 agentmods add skills/extra-org/extra/project-architecturenpx skills add extra-org/extra --skill project-architecturegit clone --depth 1 https://github.com/extra-org/extraWhat 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 | $0.00032 | $0.00547 |
| Opus 5 | $0.00016 | $0.00273 |
| Sonnet 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 3d 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.
- 3d 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 (108 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 547 once invoked, about $0.0002 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-30.
Other skills, from other repositories
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.
skill-intent-contract
Use when starting a complex or ambiguous task that risks scope drift.
bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.