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/inetgas/arch-compiler/implementing-architecturenpx skills add inetgas/arch-compiler --skill implementing-architecturegit 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/skills/inetgas/arch-compiler/implementing-architecture)<a href="https://agentmods.dev/skills/inetgas/arch-compiler/implementing-architecture"><img src="https://agentmods.dev/badge/skills/inetgas/arch-compiler/implementing-architecture.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.11180 |
| Opus 5 | $0.00026 | $0.05590 |
| Sonnet 5 | $0.00010 | $0.02236 |
| Haiku 4.5 | $0.00005 | $0.01118 |
Grade A, and why
implementing-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 — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Pattern Implementer
Overview
Translates approved architecture artifacts into working code. The architecture folder is the authoritative source for HOW to build — which services, which config, which constraints. It does NOT replace functional requirements, which tell you WHAT to build (business logic, features, API contracts). You need both.
Repo Structure — Read This First
Treat the compiler repo as having this contract:
arch-compiler/
├── README.md
├── AGENTS.md
├── README-AGENTS.md
├── tools/ <-- read-only for agents
├── schemas/ <-- read-only for agents
├── config/ <-- read-only for agents
├── scripts/ <-- read-only for agents
├── patterns/ <-- read-only for agents
└── skills/
├── using-arch-compiler/
│ └── SKILL.md
├── compiling-architecture/
│ └── SKILL.md
└── implementing-architecture/
└── SKILL.md
Before acting:
- Read
AGENTS.mdfor repo-wide agent rules and boundaries. - Read this
SKILL.mdfor the task-specific workflow. - Treat
tools/,schemas/,config/, andpatterns/as read-only unless the human explicitly asks for compiler-maintenance work in this repo. - Use this skill only when
docs/architecture/already exists and is approved. If architecture is missing or unapproved, switch toskills/compiling-architecture/SKILL.mdinstead of inventing architecture choices.
The important split is:
AGENTS.md= global agent rules for this reposkills/using-arch-compiler/SKILL.md= workflow routerskills/compiling-architecture/SKILL.md= how to compile and finalise architectureskills/implementing-architecture/SKILL.md= how to implement an already-approved architecture
When to Use
- You have a
docs/architecture/folder with approved artifacts - You are about to write code and need to know which technology choices are authorised
- You have an existing prototype or codebase and need to refactor it to conform to an approved architecture
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 · 532 lines · 51 tokens per session scan A c1f64d61aac4
implementing-architecture is a skill published in the GitHub repository inetgas/arch-compiler (10 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 11,180 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-31.
Other skills, from other repositories
deploy-registry-server-with-cnpg
Deploy the ToolHive Registry Server to a Kind cluster with CloudNativePG (CNPG) PostgreSQL database. Use when you need a production-like PostgreSQL setup with the CNPG operator.
deploy-registry-server-with-otel
Deploy the ToolHive Registry Server to a Kind cluster with telemetry enabled. Use when you need to deploy the registry server for testing with OTEL metrics and tracing.
classification-at-scale
Classify an internal catalog against a standard taxonomy at scale using deterministic providers, tri-state signals, batch group review, and a trust flywheel — LLM judgment only for configs, ambiguous tails, and critique.
review-thread
Record review verdicts and run the StateNote review thread on an agent-operation instance — every ReviewRequest verdict is one atomic batch-direct-write that advances status and co-writes a reviewnote explaining why, and findings are corrected by appending notes rather than editing them.
create-state
Create a new Cruxible state from raw domain data through staged graph, workflow, query, and review-loop design.
overlay-and-fit
Create an overlay from a published reference state, use the inherited state plus any applied kit with the lowest-friction path, and only add local config or code when the current overlay is not enough.