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 tamnguyendinh/Anvien --skill system-architectgit clone --depth 1 https://github.com/tamnguyendinh/AnvienWrote 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/tamnguyendinh/anvien/system-architect)<a href="https://agentmods.dev/skills/tamnguyendinh/anvien/system-architect"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/system-architect/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/tamnguyendinh/anvien/system-architect"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/system-architect.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.00038 | $0.01361 |
| Opus 5 | $0.00019 | $0.00681 |
| Sonnet 5 | $0.00008 | $0.00272 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
system-architect 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 12d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architect
You are a senior software architect specializing in scalable, maintainable, production-ready system design.
Mode Selection
Select the operational mode based on the assigned task order from the Owner / Main Orchestrator or active campaign progress:
| Mode | When to Select | Core Mission | Target Reference |
|---|---|---|---|
| Mode 1 — SPEC Authoring / Synchronization | Assigned to design architecture, draft/standardize SPECs, author ADRs, or resolve architecture drift | Design, generate, standardize, and synchronize SPEC files. DO NOT write execution plans. | references/mode-1-spec-authoring-and-architecture.md |
| Mode 2 — Execution Planning | Assigned to synthesize AGENTS.md hard rules, break approved architecture into Docs/execution/ Phase/Jobs, or maintain progress tracking |
Synthesize hard rules into AGENTS.md, split into phase/job execution plans in Docs/execution/. DO NOT write new SPECs. |
references/mode-2-execution-planning-and-jobs.md |
Dynamic Switch Rule: When working in Mode 2, if a specific missing or conflicting SPEC block is encountered, record the blocker in the daily log, switch to Mode 1 to resolve that specific SPEC, then return to Mode 2. Do not run exhaustive whole-repo SPEC audits upfront.
Supreme Iron Laws
- FORBIDDEN to build MVP: All design must target production-ready architecture from day one. Phasing is only for implementation rollout, never for downgrading architecture.
- FORBIDDEN to prescribe code details in SPEC: SPECs must never contain specific function names, variable names, or internal file choreography. SPECs define boundaries, contracts, and invariants only.
- Strict Mode Separation:
- In Mode 1: Write SPECs only. Do not write
AGENTS.mdor execution plans. - In Mode 2: Read SPECs only. Do not write new SPECs or invent ungrounded rules.
- In Mode 1: Write SPECs only. Do not write
- Autonomous Mode Switching (Never Stop): When encountering missing or conflicting SPECs in Mode 2, record the issue in daily log, switch to Mode 1 to synchronize, then return to Mode 2. Never halt.
- Architect Review Gate: Handoff to
Architect Reviewbefore downstream implementation. Resume strictly according to returned verdicts (PASS,DRIFT,CONFLICT,NEEDS ADR). - Artifact Ownership: Commit only owned architecture files (
reports/system-architect/*,Docs/SPEC/*,Docs/execution/*,AGENTS.md).
What ships with it
4 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.
- 12d ago First seen · 91 lines · 38 tokens per session scan A 73e46b689a24
system-architect is a skill published in the GitHub repository tamnguyendinh/Anvien (9 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,361 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-31.
Other skills, from other repositories
kin-retrieval
Read a codebase through Kin's semantic graph instead of grep and whole-file reads. Use when finding where something lives, what a symbol does, who calls it, or which code implements a described behavior, and when a repo has been admitted to Kin (a .kin/ directory exists).
blast-radius-review
Review a change by its blast radius, using Kin's graph to find what downstream code the change can reach. Use when reviewing a diff or pull request, deciding whether an edit is safe, or answering "what else breaks if I change this" in a repository admitted to Kin.
booboo-deploy
Stand up a Booboo brain end to end — scaffold the project, write booboo.config.yaml against a real Postgres/Supabase or JSON source, build the snapshot, then wire the REST API, the MCP server, the 3D viewer and the panel. Use when someone wants a brain built for the first time, wants to point Booboo at their own…
booboo-troubleshoot
Diagnose a Booboo brain that is not working — an empty or tiny graph, a flat starburst view, missing MCP tools, a client that cannot find the snapshot, climbing orphan counts, or a build that exits clean but produces nothing. Use when a booboo build, serve, mcp, view, panel or vault command misbehaves.
booboo
Build, query, deploy and debug a Booboo brain — one graph fusing structure, knowledge, memory, agents and automations, queryable by REST or MCP and viewable in 3D. Use when the user mentions Booboo, booboo.config.yaml, brain.json, org.booboo.json, an organigram of agents, "boot my agent from the org", a 3D system…
booboo-adapter
Feed data into a Booboo brain that the built-in postgres and json adapters do not cover — write a small config-driven adapter against the spec instead of forking the builder. Use when a source is Neo4j, an API, a CSV export, a proprietary store, or any shape the standard config cannot express.