What is implementing-architecture?

A procedure for turning an approved software architecture into working code. The architecture describes how the system should be built, while functional requirements describe what it must do.

Use it when a project has an approved architecture file and you need to implement that design while respecting the repository’s structure and read-only areas.

It gives implementation work a defined source of truth for services, configuration, and constraints.

implementing-architecture — Skill for Claude Code and Codex by inetgas

Install

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.

Any agent

npx skills add inetgas/arch-compiler --skill implementing-architecture

Clone the repo

git clone --depth 1 https://github.com/inetgas/arch-compiler

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/inetgas/arch-compiler/implementing-architecture/github.svg)](https://agentmods.dev/skills/inetgas/arch-compiler/implementing-architecture)

Your own site

<a href="https://agentmods.dev/skills/inetgas/arch-compiler/implementing-architecture"><img src="https://agentmods.dev/badge/skills/inetgas/arch-compiler/implementing-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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 11,180 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00051	$0.11180
Opus 5.5	$0.00020	$0.04472
Sonnet 5.5	$0.00010	$0.02236
Haiku 4.5	$0.00005	$0.01118

Measured 1mo ago against content hash c1f64d61aac4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

skills/implementing-architecture/SKILL.md · 532 lines

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.md for repo-wide agent rules and boundaries.
Read this SKILL.md for the task-specific workflow.
Treat tools/, schemas/, config/, and patterns/ 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 to skills/compiling-architecture/SKILL.md instead of inventing architecture choices.

The important split is:

AGENTS.md = global agent rules for this repo
skills/using-arch-compiler/SKILL.md = workflow router
skills/compiling-architecture/SKILL.md = how to compile and finalise architecture
skills/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

Read the full file on GitHub · 532 lines

Changes

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 · 532 lines · 51 tokens per session scan A c1f64d61aac4

Subscribe to this mod's changes

implementing-architecture is a skill published in the GitHub repository inetgas/arch-compiler (10 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 11,180 once invoked, about $0.0002 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.

Planning agent-skills ai-governance architectural-decision-records architecture architecture-as-code architecture-harness governance implementation verification

ai-loop

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

sickn33/agentic-awesome-skills · 28 tokens

architecture-paradigms

Selects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.

athola/claude-night-market · 33 tokens

data-mesh-expert

Expert-level data mesh architecture, domain-oriented ownership, data products, federated governance, and self-serve platforms. Use when the user mentions architecture, domain driven, data products, governance, or platform, or when the task involves Data Mesh Principles, Domain-Oriented Data Ownership, Data as a…

personamanagmentlayer/pcl · 75 tokens

implementing-architecture