loadout: Instructions file for Claude Code

CLAUDE.md

loadout CLAUDE.md is an instructions file for Claude Code from AmElmo/loadout. It costs 1,780 tokens per session, scanned A, original, MIT.

A project guide for Loadout, a Tauri desktop app with a React frontend and Rust backend. It describes the code layout, tools, commands, and test fixtures.

In plain words
What is it for?
Use it when changing Loadout, finding frontend or backend code, starting the app, building it, or working with its demo and empty test data.
Why use it?
It gives a coding agent the project-specific context needed to navigate the code and run the right development and test commands.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code; mentions Codex; built for cline.

This is AmElmo/loadout's own configuration. It tells Claude Code 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 AmElmo/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/AmElmo/loadout/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/AmElmo/loadout

Made for: Claude Code.

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 CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/amelmo/loadout/claude-md"><img src="https://agentmods.dev/badge/instructions/amelmo/loadout/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,780 This file is loaded in full into every session.
When invoked 1,780 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.01780 $0.01780
Opus 5.5 $0.00712 $0.00712
Sonnet 5.5 $0.00356 $0.00356
Haiku 4.5 $0.00178 $0.00178

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

Security

Grade A, and why

loadout CLAUDE.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 2mo 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.

CLAUDE.md · 129 lines

How it starts

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

Loadout

A Tauri 2.x desktop application with React + Vite frontend.

Project Structure

  • src/ - React frontend (Vite)
    • src/components/ - React UI components
    • src/lib/api/ - Frontend-backend communication wrappers (e.g., mcps.ts)
    • src/stores/ - Zustand state management stores
    • src/types/ - TypeScript interfaces (mirror Rust structs)
  • src-tauri/ - Rust backend (Tauri 2.x)
    • src-tauri/src/commands/ - Tauri command handlers
    • src-tauri/src/parsers/ - Configuration file parsers
    • src-tauri/src/scanners/ - File system scanners
  • issues/ - Task breakdown and specs with Acceptance Criteria, Technical Details, and Test Plans

Tech Stack

  • Frontend: React, Vite, Tailwind CSS, Zustand, TanStack Query
  • Backend: Rust, Tauri 2.x
  • Package Manager: pnpm

Key Commands

pnpm tauri dev           # Start development (both frontend and backend)
pnpm tauri:dev:fixtures  # Start dev with demo fixtures (uses LOADOUT_HOME)
pnpm tauri:dev:empty     # Start dev with empty fixtures (all empty states)
pnpm build               # Build frontend only
pnpm tauri build         # Build full application

Test Fixtures

fixtures/home/ contains a realistic mock home directory with configurations for Claude, Codex, and Gemini (skills, rules, hooks, MCPs, and project-level settings). Use pnpm tauri:dev:fixtures to run the app against these fixtures instead of your real home directory. fixtures/empty/ is a bare directory with no AI tool configs — use pnpm tauri:dev:empty to see all empty states across the UI. The LOADOUT_HOME env var is only honored in debug builds.

AI Tools Documentation

docs/ai-tools-reference.md maps every supported tool (Claude, Codex, Gemini, Cursor, Copilot, Windsurf, Roo, Cline, Kilo, OpenCode) and concept (MCPs, skills, agents, hooks, prompts, plugins, commands) to its official documentation URL. When modifying scanners, parsers, or fixture data for any AI tool, always consult this reference and verify against live docs using context7 or web search — config formats change frequently and the reference file may lag behind.

Read the full file on GitHub · 129 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. 2mo ago First seen · 129 lines · 1,780 tokens per session scan A f3ac8707b68d

Subscribe to this mod's changes

loadout CLAUDE.md is an instructions file published in the GitHub repository AmElmo/loadout (12 stars, last pushed 7mo ago), licensed MIT. It adds 1,780 tokens to every session, about $0.0071 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

loadout CLAUDE.md compared with instructions from other repositories

loadout CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
loadout CLAUDE.mdAmElmo/loadoutInstructions file127mo agoMITA1,780Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,685GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot