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/jaakla/openmapstack/agents-mdgit clone --depth 1 https://github.com/jaakla/openmapstackWrote 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/jaakla/openmapstack/agents-md)<a href="https://agentmods.dev/instructions/jaakla/openmapstack/agents-md"><img src="https://agentmods.dev/badge/instructions/jaakla/openmapstack/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.01820 | $0.01820 |
| Opus 5 | $0.00910 | $0.00910 |
| Sonnet 5 | $0.00364 | $0.00364 |
| Haiku 4.5 | $0.00182 | $0.00182 |
Grade A, and why
openmapstack 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 yesterday.
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is the canonical maintainer guide for coders (including AI coding agents) working on the OpenMapStack repository. Keep repository-wide development guidance here and keep it vendor-neutral.
What this repository is
OpenMapStack is a managed agent-skill codebase, not an OpenMapStack GIS analysis project.
The repository develops and quality-assures a distributable geospatial agent skill:
SKILL.mdandreferences/are product artifacts consumed by agents in other projects.templates/andexamples/define and demonstrate the artifacts the skill should cause those agents to produce.openmapstack/is executable support code for validating, running, inspecting, and verifying those artifacts.evals/measures whether the skill and its supporting contract produce correct, reproducible behavior.tests/tests the repository's Python implementation and eval infrastructure.
Do not treat SKILL.md as maintainer instructions for this repository. Read or edit it when the task concerns the shipped skill behavior, but do not preload or follow its GIS workflow merely because you are modifying this codebase.
Sources of truth
Read only what is relevant to the current issue.
| Area | Source of truth |
|---|---|
| Shipped agent behavior | SKILL.md |
| Detailed shipped guidance | references/*.md |
| Reproducible project contract | references/project-spec.md |
| Project templates | templates/ |
| Canonical worked integration example | examples/tartu-development/ |
| CLI, schema handling, reusable checks | openmapstack/ |
| Eval architecture, cases, scoring, live adapters | evals/README.md, evals/ |
| Maintainer architecture/rationale/debugging knowledge | docs/maintainers/ |
| Implementation tests | tests/ |
| User-facing install and usage docs | README.md |
Prefer the code/schema/test that owns a behavior over a prose summary elsewhere. Avoid duplicating detailed rules between files; link to the authoritative source instead.
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.
- yesterday First seen · 147 lines · 1,820 tokens per session scan A 65da789b13a4
openmapstack AGENTS.md is an instructions file published in the GitHub repository jaakla/openmapstack (68 stars, last pushed yesterday), licensed MIT. It adds 1,820 tokens to every session, about $0.0091 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-09-03.
Other instructions, from other repositories
openscreen AGENTS.md
AGENTS.md instructions for getopenscreen/openscreen, covering agents.md, setup commands, development principles, project layout and code style.
Claw3D AGENTS.md
Instructions for iamlukethedev/Claw3D, covering agent instructions, cursor cloud specific instructions, service overview, running the app and lint, typecheck, and tests.
claude-ads CLAUDE.md
Instructions for AgriciDaniel/claude-ads, covering claude ads repository instructions, architecture, development and verification.
openstatus AGENTS.md
AGENTS.md instructions for openstatusHQ/openstatus, covering agents.md, verify your change, toolchain, architecture and tests.
openstatus CLAUDE.md
Claude Code instructions for openstatusHQ/openstatus, covering claude.md and investigating production with polylane.
abap2UI5 CLAUDE.md
Claude Code instructions for abap2UI5/abap2UI5: All project guidance lives in AGENTS.md — the single source of truth for this repository (architecture and the layered design, the src/00-99 packages, the generated app/webapp mirror, the build and delivery pipeline, the CI gates and ABAP code style).