loadout: Instructions file for GitHub Copilot

.github/instructions/rust.instructions.md

loadout rust.instructions.md is an instructions file for GitHub Copilot from stefaniuk/loadout. It costs 4,442 tokens per session, scanned A, original, MIT.

A set of rules for writing and maintaining Rust code. Rust is a programming language often used for command-line tools, web services, libraries, embedded systems, and WebAssembly.

In plain words
What is it for?
Building or reviewing Rust command-line tools, services, libraries, async programs, embedded software, WebAssembly, and Tauri backends.
Why use it?
Rust projects can involve difficult choices about error handling, async code, APIs, and architecture that the compiler alone cannot decide. These instructions make those decisions consistent and documented.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is stefaniuk/loadout's own configuration. It tells GitHub Copilot how to work on loadout itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything loadout configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/stefaniuk/loadout/main/.github/instructions/rust.instructions.md
Clone the repo
git clone --depth 1 https://github.com/stefaniuk/loadout

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for loadout rust.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/stefaniuk/loadout/rust/github.svg)](https://agentmods.dev/instructions/stefaniuk/loadout/rust)
Your own site
<a href="https://agentmods.dev/instructions/stefaniuk/loadout/rust"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/rust/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.

agentmods 80×15 button for loadout rust.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/stefaniuk/loadout/rust"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/rust.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,442 This file is loaded in full into every session.
When invoked 4,442 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04442 $0.04442
Opus 5.5 $0.01777 $0.01777
Sonnet 5.5 $0.00888 $0.00888
Haiku 4.5 $0.00444 $0.00444

Measured 1mo ago against content hash 9dac85bdff4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loadout rust.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.

.github/instructions/rust.instructions.md · 287 lines

How it starts

The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Rust Engineering Instructions 🦀

These instructions define Rust-specific engineering patterns beyond what the Rust Book, compiler, and Clippy already enforce.

They must remain applicable to:

  • CLI applications and system tools
  • Web services and APIs (Actix, Axum, Rocket)
  • Libraries and shared crates
  • Async applications (Tokio, async-std)
  • Embedded and systems programming
  • WebAssembly and Tauri backends

This file does not restate Rust fundamentals (ownership, borrowing, Result, Option, ? operator). Those are assumed knowledge. It covers decision criteria, thresholds, and patterns that require human judgement.

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 [RS-<prefix>-NNN], where the prefix maps to the containing section (for example QR for Quick Reference, DEC for Decisions, ASY for Async, API for API Design). 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.

  • [RS-QR-001] Function size: split functions exceeding ~50 lines or 3 levels of nesting ([RS-STR-001]).
  • [RS-QR-002] Clone acceptance: clone() is acceptable for small Copy-like types, startup paths, or when profiler shows no impact ([RS-DEC-003]).
  • [RS-QR-003] No blocking in async: never call blocking IO or hold locks across .await ([RS-ASY-001], [RS-ASY-003]).
  • [RS-QR-004] Cancellation safety: document whether async functions are cancellation-safe ([RS-ASY-005]).
  • [RS-QR-005] Error types: libraries return typed errors; binaries may use anyhow ([RS-ERR-001]).
  • [RS-QR-006] Unsafe review: all unsafe blocks require a // SAFETY: comment and dedicated review ([RS-SAF-001]).
  • [RS-QR-007] No warnings in CI: #![deny(warnings)] or equivalent in CI; fix, don't suppress ([RS-QG-001]).
  • [RS-QR-008] Feature flag hygiene: test with --no-default-features and --all-features ([RS-ORG-004]).
  • [RS-QR-009] Structured logging: use tracing for structured logs; follow the baseline field requirements ([RS-OBS-001]).
  • [RS-QR-010] CLI contract: exit codes follow 0/1/2 contract; stdout for results, stderr for diagnostics ([RS-CLI-001]).

Read the full file on GitHub · 287 lines

Changes

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.

  1. 1mo ago First seen · 287 lines · 4,442 tokens per session scan A 9dac85bdff4b

Subscribe to this mod's changes

loadout rust.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed yesterday), licensed MIT. It adds 4,442 tokens to every session, about $0.0178 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.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,257 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

deepseek-ai/deepseek-harness · 4,159 tokens