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.
git clone --depth 1 https://github.com/inetgas/arch-compilerWrote 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/commands/inetgas/arch-compiler/compile-architecture)<a href="https://agentmods.dev/commands/inetgas/arch-compiler/compile-architecture"><img src="https://agentmods.dev/badge/commands/inetgas/arch-compiler/compile-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/commands/inetgas/arch-compiler/compile-architecture"><img src="https://agentmods.dev/badge/commands/inetgas/arch-compiler/compile-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00013 | $0.00116 |
| Opus 5.5 | $0.00005 | $0.00046 |
| Sonnet 5.5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
compile-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 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.
What it actually says
Read and follow ~/.claude/arch-compiler/skills/compiling-architecture/SKILL.md.
Use it when the user wants to select architecture patterns, compile a spec, iterate on constraints or NFRs, audit why patterns were selected or rejected, or finalize an architecture for implementation.
If the repo is installed somewhere else, substitute that stable local path before proceeding.
Do not skip the skill's setup and gating steps. Treat the skill file as the authoritative workflow.
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 First seen · 12 lines · 13 tokens per session scan A a3424d48da88
compile-architecture is a command published in the GitHub repository inetgas/arch-compiler (10 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 116 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-31.
Other commands, from other repositories
aws-research
Research AWS services and architecture patterns using AWS Knowledge MCP for authoritative guidance.
azure-research
Research Azure services and architecture patterns using Microsoft Learn MCP for authoritative guidance.
gcp-research
Research Google Cloud services and architecture patterns using Google Developer Knowledge MCP for authoritative guidance.
caio
Chief AI Officer review — AI/ML governance, model lifecycle, responsible AI, LLM integration patterns.
cfo
Chief Financial Officer review — cloud cost optimization, resource efficiency, billing logic, compute waste.
cio
Chief Information Officer review — data governance, system integration, information architecture, schema management.