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/kreek/consult/architecturenpx skills add kreek/consult --skill architecturegit clone --depth 1 https://github.com/kreek/consultWrote 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/kreek/consult/architecture)<a href="https://agentmods.dev/skills/kreek/consult/architecture"><img src="https://agentmods.dev/badge/skills/kreek/consult/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.1 | $0.00017 | $0.00931 |
| Opus 5 | $0.00009 | $0.00465 |
| Sonnet 5 | $0.00003 | $0.00186 |
| Haiku 4.5 | $0.00002 | $0.00093 |
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 yesterday.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture
Iron Law
ORGANIZE BY WHAT CHANGES TOGETHER. BOUNDARIES EXPOSE CONTRACTS, NOT INTERNAL STEPS.
When to Use
- Choosing between feature-oriented organization and horizontal controller/service/repository/DTO layers.
- Choosing shared project, package, or module boundaries, bounded contexts, and public surfaces.
- Choosing API style or data store family before a specialist skill owns the detailed shape.
- Deciding whether DDD tactical patterns earn their keep.
- Reviewing code where one behavior is scattered across many files for no technical reason.
When NOT to Use
- Data shape, invariant, and effect discipline; use
domain-modeling. - Public HTTP contract details; use
api. Physical schema; usedatabase. - Reshaping existing code while preserving behavior; use
refactoring. - Local file moves or private helper extraction that create no shared boundary: explain the choice and proceed.
Rules
- Feature behavior, data shapes, invariants, and tests live close enough to change together, and one focused behavior can be run without invoking the whole suite.
- Functions do one thing, stay around 25-30 lines, and keep conditionals and loops under three nesting levels. Guard clauses, extraction, or composition come before another nested branch.
- Horizontal layers exist only for a real boundary: process, deploy, trust, persistence, transport, or proven duplication. A layer that scatters one behavior by default is harmful.
- A module boundary says what crosses it, what assumptions hold, and what callers must not depend on. Callers depend on the contract, never the internal shape.
- Data flow is explicit: where external data enters, where it becomes trusted, where domain work happens, what output shape leaves. These are roles, not required folders. Raw external payloads do not leak past the parse boundary.
- DDD patterns (aggregates, repositories, factories, domain services) and bounded contexts are used only when they protect a real invariant, workflow, or a word that means different things in different places.
- Shared structure is user-owned. Project layout, package/module boundaries,
public library shape, and cross-component ownership future work will
depend on route through
contract-first, which owns the approval scope. - Decisions future readers cannot recover from the code (why this boundary, why this shape, what was rejected) are recorded in an ADR, comment, or commit message.
What ships with it
1 file 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.
- yesterday Changed · -53 lines 536b4a603a3f
- 5d ago First seen · 133 lines · 17 tokens per session scan A c5fc7fc24ebe
architecture is a skill published in the GitHub repository kreek/consult (1 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 931 once invoked, about $0.0001 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
clarify
Lightweight spec clarification scan for jig projects — a six-category ambiguity audit that asks up to five prioritized questions and appends them to the spec's ## Clarifications section. Auto-triggers when you say clarify this spec, audit this spec for ambiguities, is this spec ready for review, find unknowns in this…
explain
Explain jig vocabulary and artifacts in plain language. Three modes: term mode defines one lexicon term; artifact mode walks through a spec or ADR and its linked references; passage mode explains pasted jig output. Output is ephemeral (chat-only). Auto-triggers when you say explain this term, walk me through this…
arch-review
Team baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to…
pr-review
Team baseline for PR and code review — produces scope, blockers, nits, and strengths. Auto-triggers when you say review this PR, check this diff, review these changes, pre-review before I share, what do you think of this PR, or review the diff on this branch. Defers to any other installed skill whose description…
icon-composer-app-icon-workflow
Design, preview, validate, and integrate Apple app icons with Icon Composer. Use when a task mentions Icon Composer, .icon documents, Liquid Glass app icons, ictool preview exports, app icon design for iOS, iPadOS, macOS, or watchOS, or guided Icon Composer GUI work through Computer Use.
bootstrap-xcode-workspace
Create, adopt, extend, and align one Swift product workspace with app, extension, package, and service components under one permanent Xcode entrypoint.