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/taurigit 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.02451 | $0.02451 |
| Opus 5 | $0.01226 | $0.01226 |
| Sonnet 5 | $0.00490 | $0.00490 |
| Haiku 4.5 | $0.00245 | $0.00245 |
Grade A, and why
loadout tauri.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 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri Engineering Instructions 🖥️
These instructions define Tauri-specific integration patterns for building secure, performant desktop applications with a Rust core and web-based UI.
They must remain applicable to:
- Tauri v2 desktop applications
- Cross-platform builds (Windows, macOS, Linux)
- Applications requiring filesystem access, IPC, and system integration
- Enterprise distribution with signing and updates
For general language guidance, defer to:
- rust.instructions.md - Rust idioms, error handling, patterns
- reactjs.instructions.md - React component design, hooks, state
- typescript.instructions.md - TypeScript strictness, typing patterns
This file covers only what those files do not: the Tauri security model, IPC design, capability configuration, and desktop-specific integration concerns.
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 [TAU-<prefix>-NNN], where the prefix maps to the containing section (for example QR for Quick Reference, SEC for Security Model, IPC for IPC Patterns, CAP for Capabilities). 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.
- [TAU-QR-001] Least privilege: grant only required capabilities per window; never enable everything for convenience ([TAU-CAP-001]).
- [TAU-QR-002] Strict CSP: maintain strict Content Security Policy; never weaken it to "make something work" ([TAU-SEC-001]).
- [TAU-QR-003] No remote content: do not load remote scripts/CDNs in production; local assets only ([TAU-SEC-003]).
- [TAU-QR-004] UI is untrusted: all privileged operations belong in Rust; treat frontend input as hostile ([TAU-SEC-005]).
- [TAU-QR-005] Commands for request/response: use Tauri commands for discrete operations ([TAU-IPC-001]).
- [TAU-QR-006] Events for streaming: use events for progress, batches, and state changes ([TAU-IPC-002]).
- [TAU-QR-007] Operation IDs: tag all long-running work with an
op_idfor tracking and cancellation ([TAU-IPC-005]). - [TAU-QR-008] Cleanup listeners: always unregister event listeners on component unmount ([TAU-IPC-008]).
- [TAU-QR-009] Stream large results: never return huge arrays from commands; batch via events ([TAU-IPC-003]).
- [TAU-QR-010] Sign updates: if using the updater, signatures are mandatory and cannot be disabled ([TAU-DST-003]).
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 · 174 lines · 2,451 tokens per session scan A 7f1a81108e8e
loadout tauri.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 4d ago), licensed MIT. It adds 2,451 tokens to every session, about $0.0123 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 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).