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/agents-mdgit clone --depth 1 https://github.com/Indemnity83/logisticsWhat 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.07953 | $0.07953 |
| Opus 5 | $0.03977 | $0.03977 |
| Sonnet 5 | $0.01591 | $0.01591 |
| Haiku 4.5 | $0.00795 | $0.00795 |
Grade A, and why
logistics AGENTS.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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to codex 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/1.21.1- Stable releases for MC 1.21.1, maintenance focusmc/1.21.11- Stable releases for MC 1.21.11, active feature developmentmc/26.1- Snapshot development for MC 26.1 snapshots, forward-port for testing
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)
- ✅ 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
The current working directory path indicates which branch you're on.
Benefits:
- Reference code across versions without switching branches
- Compare implementations when cherry-picking
- Resolve conflicts by viewing other version's code directly
If worktrees are detected at these paths, they may be referenced when working on cross-version changes.
Development Strategy
mc/1.21.11: Primary development target (latest stable release, most players)mc/26.1: Port features to keep up with snapshot releasesmc/1.21.1: Backport features/fixes (many tech mod users still on this version)
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.
- 2d ago First seen · 624 lines · 7,953 tokens per session scan A a23338cdcb73
logistics AGENTS.md is an instructions file published in the GitHub repository Indemnity83/logistics (5 stars, last pushed 4d ago), licensed MIT. It adds 7,953 tokens to every session, about $0.0398 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
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.
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).
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.