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/hautc-it/cil/architecturenpx skills add hautc-it/cil --skill architecturegit clone --depth 1 https://github.com/hautc-it/cilWrote 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/hautc-it/cil/architecture)<a href="https://agentmods.dev/skills/hautc-it/cil/architecture"><img src="https://agentmods.dev/badge/skills/hautc-it/cil/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.00050 | $0.00345 |
| Opus 5 | $0.00025 | $0.00172 |
| Sonnet 5 | $0.00010 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
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 5d 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
Skill: Architecture
Service boundaries and structural decisions.
Decision Framework
Before adding a component or crossing a boundary, ask:
- Cohesion — Do these things always change together? If yes, keep together.
- Coupling — What depends on this? Can I change the implementation without changing callers?
- Ownership — Who owns this data? Is there a single source of truth?
- Boundary — What crosses this boundary? Can I state it in one sentence?
If you can't explain a boundary in one sentence, it's wrong.
Dependency Direction
Domain (core logic)
← Application (use cases)
← Infrastructure (DB, HTTP, IO)
← Entry points (CLI, API, events)
Domain has zero infrastructure dependencies.
Heuristics
- Small interfaces > large interfaces. Narrow contracts, stable contracts.
- Composition > inheritance. Prefer has-a over is-a.
- Duplication < wrong abstraction. Wait for the third occurrence.
- If two services always deploy together, merge them.
- If one change requires updating many files, the abstraction is wrong.
Anti-patterns
- Circular dependencies (A → B → A)
- God object (everything depends on one thing)
- Shared mutable state across boundaries
- Premature abstraction (abstract before you see the pattern)
- Distributed monolith (microservices with synchronous coupling)
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.
- 5d ago First seen · 47 lines · 50 tokens per session scan A 15a756d564ba
architecture is a skill published in the GitHub repository hautc-it/cil (1 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 345 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
OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the…
glossary-init
USE WHEN setting up a repo for AI-first work, when an agent hallucinates domain term meaning, or when user asks to bootstrap / extend the repo's domain glossary. Surfaces candidate terms by identifier frequency, asks the user for 1-sentence definitions, writes GLOSSARY.md at repo root. Idempotent — re-running adds new…
codex-pair-resume
Resume codex-pair for this project after a previous pause. Removes .codex-pair/state/paused and clears failure state. Review resumes on the next supported file edit; missing state is a no-op.
repo-visuals
Create hero visuals — animated GIF, static PNG, or animated SVG — for GitHub repositories. Runs a structured discovery conversation (scan repo → recommend format → propose creative scenarios → agree on a brief), then designs bespoke HTML/SVG, previews it in the browser, and exports. Use when the user asks for a README…
generate-tests
Generate unit tests for a .NET service following the coverage-kit conventions. Use when the user asks to 'generate tests', 'backfill tests', 'characterize this service', or 'add tests for' a target after coverage-init has run. Operates in characterization mode (freeze current behavior for existing code) or spec mode…
conventions-init
USE WHEN setting up a repo for AI-first work (after /init-repo), or when the context-surface hook should start feeding repo conventions to agents before edits. Drafts conventions.yml at repo root: per-kind casing (inferred from the code), a vague-name denylist seed, directory roles, and a hand-filled house-rules…