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.00069 | $0.01871 |
| Opus 5 | $0.00034 | $0.00936 |
| Sonnet 5 | $0.00014 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
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 11d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/as:project — Project Setup and Memory
Harness note: use
/as:<skill>on Claude Code and$<skill>on Codex. Resolve<skill-root>as the directory containing this loadedSKILL.mdand<plugin-root>as the plugin root that containsskills/, and use equivalent native tools when host tool names differ.
/as:project is the only project-memory interface. It owns current facts in PROJECT.md and durable reasoning in decisions/*.md without combining those record types or duplicating a decision index.
Commands
/as:project init
/as:project status
/as:project update
/as:project remember <information>
/as:project decisions
/as:project record-decision <choice>
/as:project supersede <number>
/as:project migrate
Hard boundaries
PROJECT.mdcontains sourced current facts. Decision identity, status, rationale, and history live only indecisions/*.md.PROJECT.mdlinks todecisions/but has no Decisions table and never copies decision metadata.- Never write
STUDIO.md./as:studioalone owns the manifest. - Never create a nested project beneath an existing
PROJECT.md. - Every durable mutation is previewed and requires affirmative confirmation.
- Preserve malformed records. A parse failure means unknown, not absent or approved.
- Use project-relative links; never persist machine-specific absolute paths.
Resolve the project root
Run <plugin-root>/skills/project/scripts/resolve-context.sh from the current or explicitly supplied directory and follow references/context-resolution.md. PROJECT.md is the only implicit project boundary. A nearer project inside a monorepo wins over outer repository metadata; typed-record directories, task/time files, Claude instructions, git roots, and the current directory never establish a project. Stop on invalid; use the validated picker for studio-picker; and never write before one exact project is resolved.
/as:project init
What ships with it
11 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.
- README.md 699 B
- references/context-resolution.md 951 B
- scripts/project-workspace.sh 7.1 KB runs code
- scripts/resolve-context.sh 4.7 KB runs code
- templates/AGENTS.md 427 B
- templates/CLAUDE.md 427 B
- templates/decision.md 198 B
- templates/PROJECT.md 880 B
- templates/record-directory-README.md 142 B
- templates/TASKS.md 117 B
- templates/TIMELOG.md 89 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.
- 11d 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 (351 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 1,871 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-30.
Other skills, from other repositories
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
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.
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…