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 projectgit 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/project)<a href="https://agentmods.dev/skills/alpacalabsllc/skills-for-architects/project"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/project/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/project"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/project.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.00033 | $0.01117 |
| Opus 5.5 | $0.00013 | $0.00447 |
| Sonnet 5.5 | $0.00007 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
project 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/as:project
Before acting, read the host contract, this component's declaration (skill:project), and applicable workspace semantics. Load only the required modes from the shared catalog.
Use the host adapter for native invocation. Apply the native workspace operations with the host’s own tools and ordinary task-specific code. Operation names identify semantic scope, not function calls or a dispatcher. No Arch Studio runner, executable download or reconstructed helper is required. Resolve canonical context before existing-workspace edits; fresh setup validates its explicit target and ancestor boundary instead. Existing exact authorization persists; ask only for material missing information or missing permission.
Own PROJECT.md current facts and documents of kind decision. The agreement skill owns only its bounded Agreement section in PROJECT.md; studio owns synchronized registered status. Decision reasoning is not duplicated into the fact manifest.
Before changing records
Before persistent changes, follow the native mutation sequence: Inspect → Prepare → Verify preparation → Apply → Verify result → Complete. Inspect pending work first. Finish and verify preparation before the first canonical write: separately reread every saved original and prepared file, check its complete actual bytes, establish durable saving, and inspect actual permissions, ownership and ACLs. Merely writing recovery files does not finish verification. Apply only that verified set. Mark complete only after fresh readback validates the entire affected result and its relationships. Read-only requests and inline drafts need no publication sequence.
What ships with it
12 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.
- host-contract.json 1.6 KB
- README.md 149 B
- references/context-resolution.md 4.3 KB
- templates/AGENTS.md 621 B
- templates/CHANGES.csv 53 B
- templates/CLAUDE.md 74 B
- templates/decision.md 296 B
- templates/DOCUMENTS.csv 149 B
- templates/INVOICES.csv 119 B
- templates/PROJECT.md 1.4 KB
- templates/TASKS.csv 102 B
- templates/TIME.csv 45 B
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 Changed · -71 lines · -36 tokens per session 3a5a41f2b4be
- 1mo ago First seen · 121 lines · 69 tokens per session scan A 0a7f90163a18
project is a skill published in the GitHub repository AlpacaLabsLLC/skills-for-architects (393 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 1,117 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
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
workspace
Scaffold and manage the stateless AI workspace — context, packs, repos, and knowledge for multi-repo orchestration.
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…
memory
Use when user invokes /memory with a subcommand (search, trace, add, episode, status). Also triggers on "search my memory for X", "add to memory", "what do I know about X" (when membrain is available), "memory status", "memory trace". Searches and manages the membrain knowledge graph via MCP tools or HTTP API.
capture
Use when user invokes /capture to capture information from the current conversation into a staging file for later reflection and knowledge graph processing. Accepts no arguments (auto-extract), specific facts as text, or filter keywords like "decisions" or "technical". Do NOT use when the user wants to write directly…