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/geleynse/gantry/agents-mdgit clone --depth 1 https://github.com/geleynse/gantryWrote 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/geleynse/gantry/agents-md)<a href="https://agentmods.dev/instructions/geleynse/gantry/agents-md"><img src="https://agentmods.dev/badge/instructions/geleynse/gantry/agents-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.01724 | $0.01724 |
| Opus 5 | $0.00862 | $0.00862 |
| Sonnet 5 | $0.00345 | $0.00345 |
| Haiku 4.5 | $0.00172 | $0.00172 |
Grade A, and why
gantry 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 4d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gantry — Agent Instructions
MCP proxy and live dashboard for Space Molt AI fleets. This file provides context for AI coding assistants working on this codebase.
Quick Reference
bun install # install dependencies (root, workspaces)
bun run build # build server + dashboard (works from root)
bun run --cwd server dev # dev mode with hot reload (server-only script)
bun run --cwd server test:isolated # full suite, one process per file (what CI gates on)
bun test <file> # single file — a full `bun test` false-reds ~60% of the time
Dashboard at http://localhost:3100.
Repository Structure
gantry/
├── server/ # Express server (MCP proxy + REST API + dashboard)
│ ├── src/
│ │ ├── proxy/ # MCP proxy modules (compound tools, pipeline, guardrails)
│ │ ├── routines/ # 18 multi-step game routines
│ │ ├── web/ # Express routes, auth adapters, middleware
│ │ ├── services/ # Database, notes, comms, analytics
│ │ ├── app/ # React 19 + Next.js 15 frontend
│ │ ├── components/ # Shared React components
│ │ ├── hooks/ # React hooks
│ │ ├── shared/ # Shared TypeScript types
│ │ ├── config/ # Config parsing and schemas
│ │ └── lib/ # Utilities (logger, api helpers)
│ ├── docs/
│ │ └── API.md # REST API documentation (CONFIG.md is a moved-stub)
│ └── scripts/ # Setup and build scripts
├── docs/ # configuration.md (canonical config reference), architecture, deployment
├── examples/
│ └── agent-template/ # Template for creating new agents
├── docker-compose.yml # Docker deployment
└── CONTRIBUTING.md # Code style, testing, PR guidelines
Architecture
AI Agent (Claude/Codex/Gemini)
│
│ MCP (HTTP)
▼
Gantry Server :3100
├── /mcp, /mcp/v2 MCP proxy (compound tools, guardrails, injections)
├── /api/* REST API (agent status, comms, analytics, notes)
└── / Web dashboard (React + Next.js, SSE streams)
│
│ MCP (HTTP)
▼
game.spacemolt.com/mcp
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.
- 4d ago First seen · 132 lines · 1,724 tokens per session scan A 19addd6a4aa5
gantry AGENTS.md is an instructions file published in the GitHub repository geleynse/gantry (3 stars, last pushed 16d ago), licensed MIT. It adds 1,724 tokens to every session, about $0.0086 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
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.