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/aws-geospatial/amazon-location-agent-context/agents-mdgit clone --depth 1 https://github.com/aws-geospatial/amazon-location-agent-contextWhat 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.02219 | $0.02219 |
| Opus 5 | $0.01110 | $0.01110 |
| Sonnet 5 | $0.00444 | $0.00444 |
| Haiku 4.5 | $0.00222 | $0.00222 |
Grade A, and why
amazon-location-agent-context 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 3d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Guide
This document covers the build system, content structure, and how to contribute new context entries.
Directory Structure
/
├── kiro-powers/ # Kiro Power (generated output)
│ └── amazon-location/
│ ├── POWER.md
│ ├── mcp.json
│ └── steering/
│ ├── address-input.md
│ ├── address-verification.md
│ └── ...
│
├── plugins/ # Claude Code Plugin (generated output)
│ └── amazon-location/
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── .mcp.json
│ └── skills/
│ └── amazon-location/
│ ├── SKILL.md
│ └── references/
│ ├── address-input.md
│ ├── address-verification.md
│ └── ... # Loaded on demand by Claude
│
├── skills/ # Agent Skills (generated output)
│ └── amazon-location-service/
│ ├── SKILL.md
│ └── references/
│ ├── address-input.md
│ ├── address-verification.md
│ └── ... # Loaded on demand by compatible tools
│
├── .claude-plugin/ # Claude Code Marketplace (generated output)
│ └── marketplace.json
│
├── context/ # Direct context (generated output)
│ ├── amazon-location.md
│ └── additional/
│ ├── address-input/
│ │ ├── BRIEF.md
│ │ └── AGENTS.md
│ └── ...
│
├── src/
│ ├── content/ # Source content (shell variables)
│ │ ├── amazon-location.sh # Core service documentation
│ │ └── additional/ # Additional context entries
│ │ ├── web-javascript.sh
│ │ ├── address-input.sh
│ │ └── ...
│ │
│ ├── templates/ # Projection templates
│ │ ├── base/ # Base context templates
│ │ │ ├── amazon-location.md
│ │ │ └── additional/
│ │ │ └── template/
│ │ │ ├── BRIEF.md
│ │ │ └── AGENTS.md
│ │ │
│ │ ├── kiro/ # Kiro Power templates
│ │ │ ├── POWER.md
│ │ │ ├── mcp.json
│ │ │ └── steering/
│ │ │ └── template.md
│ │ │
│ │ └── claude/ # Claude Code Plugin templates
│ │ ├── plugin.json
│ │ ├── marketplace.json
│ │ ├── mcp.json
│ │ └── skills/
│ │ └── amazon-location/
│ │ ├── SKILL.md
│ │ └── references/
│ │ └── template.md
│ │
│ └── scripts/ # Build scripts
│ ├── build.sh # Main build orchestrator
│ ├── build-base.sh # Build context projection
│ ├── build-kiro.sh # Build Kiro projection
│ ├── build-claude.sh # Build Claude Code projection
│ └── evaluate-context-size.sh
│
├── README.md
├── AGENTS.md
└── ...
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.
- 3d ago First seen · 264 lines · 2,219 tokens per session scan A 4c2e232b75db
amazon-location-agent-context AGENTS.md is an instructions file published in the GitHub repository aws-geospatial/amazon-location-agent-context (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 2,219 tokens to every session, about $0.0111 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.