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 instructions/stefaniuk/loadout/makefilegit 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.04857 | $0.04857 |
| Opus 5 | $0.02429 | $0.02429 |
| Sonnet 5 | $0.00971 | $0.00971 |
| Haiku 4.5 | $0.00486 | $0.00486 |
Grade C, and why
loadout makefile.instructions.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- [MK-QR-010] **Avoid common anti-patterns**: `|| true` without comment, large inline shell, hardcoded paths, unscoped `rm -rf` (§12). How it starts
The opening of the file, as written. The whole thing — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Makefile Engineering Instructions (developer experience, CI-aligned) 🛠️
These instructions define the default engineering approach for using Makefiles as orchestration, not as a place for complex logic.
They must remain applicable to:
- Small repos with a single
Makefile - Modular repos that include shared
*.mkmodules (recommended) - Repos where
makeis the canonical interface for local dev and CI/CD
They are non-negotiable unless an exception is explicitly documented (with rationale and expiry) in an ADR/decision record.
Identifier scheme. Every normative rule carries a unique tag in the form [MK-<prefix>-NNN], where the prefix maps to the containing section (for example OP for Operating Principles, LCL for Local-first developer experience, STR for Structure, UX for Target UX, SH for Shell & safety, VAR for Variables, SEC for Security, CI for CI alignment, QG for Quality Gates, and AI for AI-assisted expectations). 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.
- [MK-QR-001] Thin root Makefile: keep the top-level
Makefilesmall; push reusable logic intoscripts/**/*.mkandscripts/**/*.sh([MK-STR-001], [MK-STR-004], [MK-SH-008]). - [MK-QR-002] Help-first UX: default goal is
help; every public target has an inline description and category ([MK-UX-001]–[MK-UX-006]). - [MK-QR-003] Safe by default: no destructive behaviour without explicit scoping and confirmation options ([MK-SEC-001]–[MK-SEC-006]).
- [MK-QR-004] Fail fast: recipes must fail on errors; never hide failures ([MK-SH-001]–[MK-SH-006]).
- [MK-QR-005] CI uses make: CI/CD should call the same targets developers run locally ([MK-CI-001]–[MK-CI-006]).
- [MK-QR-006] Deterministic targets: stable outputs and consistent environment handling ([MK-OP-003], [MK-VAR-001]–[MK-VAR-006]).
- [MK-QR-007] Small, testable changes: prefer incremental improvements; do not rewrite the build system as a "clean-up" ([MK-OP-002], [MK-AI-001]).
- [MK-QR-008] Fast feedback: local development and tests must be quick and confidence-building ([MK-OP-005], [MK-LCL-001]–[MK-LCL-005]).
- [MK-QR-009] Run the quality gates after any Makefile/script change and iterate to clean ([MK-QG-001]–[MK-QG-003]).
- [MK-QR-010] Avoid common anti-patterns:
|| truewithout comment, large inline shell, hardcoded paths, unscopedrm -rf(§12).
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 · 296 lines · 4,857 tokens per session scan C 60d106971ff9
loadout makefile.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 3d ago), licensed MIT. It adds 4,857 tokens to every session, about $0.0243 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
apm cli.instructions.md
CLI Design Guidelines for visual output, styling, and user experience standards.
apm integrators.instructions.md
Architecture rules for file-level integrators (BaseIntegrator pattern).
apm cicd.instructions.md
CI/CD Pipeline configuration for PyInstaller binary packaging and release workflow.
spec-driven-steroids AGENTS.md
Instructions for lindoelio/spec-driven-steroids, covering agents.md, project identity, technology stack, essential commands and agent constraints.
featherspec constitution.instructions.md
FeatherSpec constitution editing rules (thin loader).
featherspec knowledge-records.instructions.md
FeatherSpec knowledge record rules — observation, rationale, provenance (thin loader).