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/indemnity83/logistics/claude-mdgit clone --depth 1 https://github.com/Indemnity83/logisticsWrote 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/instructions/indemnity83/logistics/claude-md)<a href="https://agentmods.dev/instructions/indemnity83/logistics/claude-md"><img src="https://agentmods.dev/badge/instructions/indemnity83/logistics/claude-md.svg" alt="Measured on agentmods" 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 | $0.11501 | $0.11501 |
| Opus 5 | $0.05751 | $0.05751 |
| Sonnet 5 | $0.02300 | $0.02300 |
| Haiku 4.5 | $0.01150 | $0.01150 |
Grade C, and why
logistics CLAUDE.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 today.
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.
rm -rf "$LOCK" # release: only ever on this path How it starts
The opening of the file, as written. The whole thing — 782 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Branch Strategy (IMPORTANT!)
FIRST: Always check your current branch using git branch --show-current or by checking the working directory path (e.g., ../logistics-mc-1.21.11/ indicates mc/1.21.11 branch).
This repository uses a multi-version strategy to support different Minecraft releases:
mc/26.3- Pre-release. Newest MC release, not yet stable. Forward-port target — receives cherry-picks frommc/26.2, does not originate new workmc/26.2- Main/default branch (the branchorigin/HEADtracks). Newest stable MC release; new work starts heremc/26.1- Maintenance + backport target for MC 26.1mc/1.21.11- Maintenance + backport target for MC 1.21.11mc/1.21.1- Maintenance + backport target for MC 1.21.1
Roles advance over time: when a newer MC release ships and is stable, main moves to that mc/2x.y branch and the previous one becomes a backport target. A pre-release branch (like mc/26.3 today) does not become main and does not shift the backport chain until it ships — it just trails main as a forward-port target. Don't hardcode which branch is main — confirm with git rev-parse --abbrev-ref origin/HEAD.
Critical Understanding
Domain architecture enables cross-version cherry-picking. After significant refactoring to isolate version-specific code:
- ✅ Can cherry-pick commits between branches (mc/1.21.1 ↔ mc/1.21.11 ↔ mc/26.1 ↔ mc/26.2 ↔ mc/26.3)
- ✅ Can share code across versions via git operations
- ✅ Can maintain feature parity with minimal manual intervention
- ✅ Cherry-pick is the primary porting mechanism
Porting = git cherry-pick, with occasional conflict resolution for API differences.
Recommended Worktree Setup
For easier cross-version development, consider setting up git worktrees for each mc/* branch in sibling directories:
../logistics-mc-1.21.1/- mc/1.21.1 branch worktree../logistics-mc-1.21.11/- mc/1.21.11 branch worktree../logistics-mc-26.1/- mc/26.1 branch worktree../logistics-mc-26.2/- mc/26.2 (main) branch worktree../logistics-mc-26.3/- mc/26.3 (pre-release) branch worktree
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.
- today Changed · +129 lines · +2,483 tokens per session scan A → C a17d805bce0c
- 4d ago First seen · 653 lines · 9,018 tokens per session scan A 8b1d6a521176
logistics CLAUDE.md is an instructions file published in the GitHub repository Indemnity83/logistics (6 stars, last pushed today), licensed MIT. It adds 11,501 tokens to every session, about $0.0575 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.