Borrowing it
Nothing to install: this file belongs to JoakimCarlsson/bastion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JoakimCarlsson/bastion/main/AGENTS.mdgit clone --depth 1 https://github.com/JoakimCarlsson/bastionWrote 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/joakimcarlsson/bastion/agents-md)<a href="https://agentmods.dev/instructions/joakimcarlsson/bastion/agents-md"><img src="https://agentmods.dev/badge/instructions/joakimcarlsson/bastion/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.1 | $0.02030 | $0.02030 |
| Opus 5 | $0.01015 | $0.01015 |
| Sonnet 5 | $0.00406 | $0.00406 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
bastion AGENTS.md scanned grade A 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **New or changed API endpoints:** start the API (`go run ./cmd/api`, `docker compose up`, or equivalent), then **`curl` every new/changed route** — assert status code and response body match acceptance criteria. How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Bastion contributor and agent contract
Read this document first before planning, implementing, or reviewing Bastion work. It is the canonical source for architecture rules and mandatory verification.
Project summary
Bastion is a co-op tower defense game: a Go API (minmux router, PostgreSQL) and a Bun + React SPA under web/. The API serves JSON endpoints and, when built, static assets from web/dist.
Hard rules — verification (non-negotiable)
- Everything observable must be verified end-to-end. Unit tests alone are not enough for HTTP APIs or running services.
- New or changed API endpoints: start the API (
go run ./cmd/api,docker compose up, or equivalent), thencurlevery new/changed route — assert status code and response body match acceptance criteria. - Delivery agents follow
.cursor/rules/subagents.mdcand.cursor/verify-commands.mdfor project-specific commands. - Coder must list every new/changed route in
HANDOFF:IMPLEMENTATION→smoke_endpointswith concreteexpectvalues. - Smoke-tester must not mark pass without live endpoint evidence when the issue touches HTTP.
Smoke example
Start the API (database optional for /health; required for /ready):
go run ./cmd/api
# or: docker compose up --build
Verify health and readiness:
curl -s http://localhost:8080/health
curl -s http://localhost:8080/ready
Expected: /health returns {"status":"ok","version":"..."} (HTTP 200). /ready returns {"status":"ready"} (HTTP 200) when the database is reachable, or HTTP 503 with {"status":"not_ready"} otherwise.
Hard rules — architecture (Go)
Package by subsystem (bounded context), not by technical layer. Top-level directories under internal/ are domain slices. Prefer flat packages with many .go files; add sub-folders only when a sub-feature has its own vocabulary and roughly 10+ files.
Do not introduce:
internal/
controllers/
services/
repositories/
models/
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.
- 6d ago First seen · 179 lines · 2,030 tokens per session scan A 8894a5056053
bastion AGENTS.md is an instructions file published in the GitHub repository JoakimCarlsson/bastion (2 stars, last pushed 3mo ago), licensed MIT. It adds 2,030 tokens to every session, about $0.0102 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.