Borrowing it
Nothing to install: this file belongs to stefaniuk/loadout. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stefaniuk/loadout/main/.github/instructions/likec4.instructions.mdgit 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/instructions/stefaniuk/loadout/likec4)<a href="https://agentmods.dev/instructions/stefaniuk/loadout/likec4"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/likec4/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.
<a href="https://agentmods.dev/instructions/stefaniuk/loadout/likec4"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/likec4.svg" alt="Reviewed on agentmods" width="80" 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.01440 | $0.01440 |
| Opus 5.5 | $0.00576 | $0.00576 |
| Sonnet 5.5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
loadout likec4.instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LikeC4 DSL Instructions (architecture-as-code diagrams) 📐
These instructions define the engineering approach for authoring LikeC4 architecture-as-code files.
They must remain applicable to:
- C4 model definitions (system context, container, component diagrams)
- Specification blocks (element kinds, relationship kinds, styles)
- View definitions and layout
- Multi-file workspace models
They are non-negotiable unless an exception is explicitly documented (with rationale and expiry) in an ADR/decision record.
Cross-references. For architecture documentation standards, see architecture-baseline.include.md. For the C4 model generation prompt, see architecture.05-c4-model.prompt.md. This file focuses exclusively on LikeC4 DSL patterns and validation.
Identifier scheme. Every normative rule carries a unique tag in the form [LC4-<prefix>-NNN], where the prefix maps to the containing section (for example QR for Quick Reference, OP for Operating Principles, SYN for Syntax, VAL for Validation, STY for Style). Use these identifiers when referencing, planning, or validating requirements.
0. Quick reference (apply first) 🧠
This section exists so humans and AI assistants can reliably apply the most important rules even when context is tight.
- [LC4-QR-001] Element syntax: use
identifier = kind 'Title'- identifier first, then=, then kind. - [LC4-QR-002] Never mix forms:
kind identifier = 'Title'is INVALID and silently drops the element. - [LC4-QR-003] Validate after generation: use LikeC4 MCP tools to confirm all elements parsed correctly.
- [LC4-QR-004] Specification first: declare every element kind in
specification {}before using it inmodel {}.
1. Operating principles 🧭
These principles extend constitution.md §3.
- [LC4-OP-001] Treat the specification as the source of truth for the architecture model. If a system, container, or component is not evidenced in the codebase, it does not belong in the diagram.
- [LC4-OP-002] Prefer small, incremental updates over full model rewrites.
- [LC4-OP-003] Design for determinism: the same model source must produce the same diagrams.
- [LC4-OP-004] Validate every change using LikeC4 MCP tools - the tooling fails silently on syntax errors.
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 · 147 lines · 1,440 tokens per session scan A 230e26ee673e
loadout likec4.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed yesterday), licensed MIT. It adds 1,440 tokens to every session, about $0.0058 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.