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/system-documentationnpx skills add stefaniuk/loadout --skill system-documentationgit clone --depth 1 https://github.com/stefaniuk/loadoutWhat 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.00048 | $0.04110 |
| Opus 5 | $0.00024 | $0.02055 |
| Sonnet 5 | $0.00010 | $0.00822 |
| Haiku 4.5 | $0.00005 | $0.00411 |
Grade A, and why
system-documentation 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Documentation Skill
This skill manages the repository documentation system as a set of canonical
artefacts instead of treating README.md as a catch-all file.
It keeps four layers distinct:
- Repository entrypoints such as
README.mdand GitHub-conventional files - Durable current-state documentation under
docs/ - Long-lived architectural decisions under
docs/adr/ - Feature-scoped intent and history under
specs/NNN-feature-name/
The skill is opinionated on purpose. Its job is to keep documentation precise, placed correctly, and aligned with implemented behaviour.
Theoretical basis
The skill combines two established frameworks with repository evidence from mature open-source projects (Django, FastAPI, Kubernetes, Backstage):
- Diátaxis (diataxis.fr) defines the four reader-needs modes - tutorials, how-to guides, reference, and explanation - and is used here as the content-quality control framework: every page must have exactly one mode.
- Docs as Code (writethedocs.org/guide/docs-as-code) defines the operating model: plain-text under version control, reviewed in pull requests, validated automatically, evolved alongside the code it documents.
Diátaxis alone does not enumerate every artefact a real software system needs. Mature repositories also keep architecture overviews, ADRs, runbooks, troubleshooting/FAQ, security policy, contribution guidance, release notes, and upgrade guides as first-class documentation. This skill therefore covers the whole documentation system, not only the four core modes.
Why this exists
Documentation usually drifts in three ways:
- canonical facts get copied into the wrong file
- public-surface changes update code but not reference material
- operational, architectural, and learning content get mixed together
This skill prevents that drift by managing documentation as a dependency- ordered system of artefacts with explicit contracts.
What ships with it
11 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.
- AGENTS.md 2.8 KB
- readme-templates.md 26 KB
- step-01-foundation.md 5.7 KB
- step-02-architecture.md 3.1 KB
- step-03-reference.md 3.5 KB
- step-04-explanation.md 2.9 KB
- step-05-how-to.md 2.8 KB
- step-06-tutorials.md 2.5 KB
- step-07-operations.md 3.2 KB
- step-08-audience-indexes.md 2.3 KB
- step-09-governance-lifecycle.md 5.9 KB
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 First seen · 391 lines · 48 tokens per session scan A 116b3b79f4c5
system-documentation is a skill published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 4,110 once invoked, about $0.0002 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
sddp-autopilot
Run the full SDD feature-delivery pipeline. Direct command-bar dispatch only; do not select for general queries.
sddp-amend
Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only; do not select for general queries.
sddp-implement-qc-loop
Run implement and QC in a continuous loop. Direct command-bar dispatch only; do not select for general queries.
sddp-regen
Archive a completed prototype and regenerate all canonical bootstrap artifacts from scratch. Direct command-bar dispatch only; do not select for general queries.
sddp-specify
Create a feature specification from a feature description. Direct command-bar dispatch only; do not select for general queries.
sddp-checklist
Generate and evaluate a requirements quality checklist. Direct command-bar dispatch only; do not select for general queries.