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/stefaniuk/loadout/architecture-docsnpx skills add stefaniuk/loadout --skill architecture-docsgit clone --depth 1 https://github.com/stefaniuk/loadoutWrote 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/stefaniuk/loadout/architecture-docs)<a href="https://agentmods.dev/skills/stefaniuk/loadout/architecture-docs"><img src="https://agentmods.dev/badge/skills/stefaniuk/loadout/architecture-docs.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.00026 | $0.01252 |
| Opus 5 | $0.00013 | $0.00626 |
| Sonnet 5 | $0.00005 | $0.00250 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
architecture-docs 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Documentation Skill
This skill generates architecture documentation following a structured six-step pipeline. Each step builds on the outputs of previous steps. Steps can be run individually or sequentially.
Step Resolution
Resolve the step from the user's input ($ARGUMENTS). Match against the table below.
| Step | Slug | Output path | Dependencies |
|---|---|---|---|
| 01 | repository-map | .copilot/analysis/repository-map.md |
None |
| 02 | component-catalogue | .copilot/analysis/component-*.md |
Step 01 |
| 03 | runtime-flows | .copilot/analysis/runtime-flow-*.md |
Steps 01–02 |
| 04 | domain-analysis | .copilot/analysis/domain-*.md |
Steps 01–03 |
| 05 | c4-model | .copilot/analysis/likec4/** |
Steps 01–04 |
| 06 | infrastructure-diagram | .copilot/analysis/infrastructure/** |
Steps 01–05 |
| all | (all steps sequentially) | All of the above | None |
If "all" is specified, run steps 01 through 06 in sequence. If a single step is specified, check that its dependency outputs exist before proceeding.
Mandatory Preparation
Before starting any step:
- Read the architecture overview instructions and adopt the approach for gathering supporting evidence.
- For step 05 (c4-model), also read the LikeC4 instructions for DSL syntax.
Goal
Produce accurate, evidence-based architecture documentation for the repository. Each step targets a specific output artefact. Update the .copilot/analysis/README.md index after each step.
Workflow Per Step
Discovery
For every step:
- Read outputs from all prior steps (if they exist) to build cumulative context.
- Run
git ls-filesandscc(if available) to enumerate the codebase. - Perform step-specific discovery as described below.
What ships with it
8 files 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.
- 3d ago First seen · 84 lines · 26 tokens per session scan A 624b101aa291
architecture-docs is a skill published in the GitHub repository stefaniuk/loadout (1 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,252 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
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
docs-impact-architect
Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume /…
spec-kitty-mission-review
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…
spec-kitty-runtime-next
Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…