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.
git 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/commands/stefaniuk/loadout/dev.implement-commands)<a href="https://agentmods.dev/commands/stefaniuk/loadout/dev.implement-commands"><img src="https://agentmods.dev/badge/commands/stefaniuk/loadout/dev.implement-commands/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/commands/stefaniuk/loadout/dev.implement-commands"><img src="https://agentmods.dev/badge/commands/stefaniuk/loadout/dev.implement-commands.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.00011 | $0.01526 |
| Opus 5.5 | $0.00004 | $0.00610 |
| Sonnet 5.5 | $0.00002 | $0.00305 |
| Haiku 4.5 | $0.00001 | $0.00153 |
Grade C, and why
dev.implement-commands 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 19d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Avoid unscoped destructive commands (for example unbounded `rm -rf`). How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Input argument: Language (for example Python, TypeScript, Go, Rust).
Goal 🎯
Audit and enforce development command discipline across the repository. Make is the canonical interface for local development and CI, and every command must be discoverable, stable, and well documented. Ensure a top-level Makefile exists and that required targets and quality checks are present, help text is consistent, and complex logic is delegated to scripts. Align all changes to:
Steps 👣
Step 1: Discover command surfaces
- Read the repository-template skill and identify the Core Make System capability and any linked capabilities that apply.
- Read and apply the rules in .github/instructions/makefile.instructions.md.
- Locate all command surfaces:
- Top-level
Makefileand any included*.mkmodules - Command scripts under
scripts/ - CI workflows that call build or test commands
- Documentation that lists developer commands
- Top-level
- Build a command map that links each target to its script(s) and intended purpose.
Step 2: Assess compliance
For each Makefile and related script, assess compliance with all categories in Implementation requirements. Identify missing targets, inconsistent naming, undocumented variables, missing help text, and any direct tool invocations in CI that bypass Make.
Step 3: Remediate
Apply fixes immediately using sensible defaults and the repository-template skill:
- Keep the root Makefile thin and include shared modules.
- Add missing required targets and wire them to scripts.
- Keep complex logic out of Make recipes.
- Ensure
make helpis the default and lists all public targets. - Align local and CI commands to use the same Make targets.
Step 4: Validate
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.
- 19d ago Changed 8a182300a2f5
- 1mo ago First seen · 148 lines · 11 tokens per session scan C 40d55306a5d3
dev.implement-commands is a command published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 13d ago), licensed MIT. It adds 11 tokens to every session and 1,526 once invoked, about $0.0000 per session on Opus 5.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-09-12.
Other commands, from other repositories
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
sddp-plan
Command description: Create an implementation plan from the current feature specification. Argument hint: [optional: planning constraints or focus areas] Command category: feature-delivery Prerequisites: spec.
sddp-prd
Command description: Create or refine the canonical product document. Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none.
sddp-qc
Command description: Run quality control against the implemented feature. Argument hint: [optional: testing focus such as unit tests, security audit, requirements sync] Command category: feature-delivery Prerequisites: spec, plan, tasks, implementation:complete.
sddp-specify
Command description: Create a feature specification from a feature description. Argument hint: [feature description] Command category: feature-delivery Prerequisites: project-instructions.
sddp-amend
Command description: Propagate a bootstrap change across canonical project artifacts and the project plan. Argument hint: [project-level change to propagate across bootstrap artifacts] Command category: project-bootstrap Prerequisites: project-instructions, product-document, technical-context, project-plan.