Borrowing it
Nothing to install: this file belongs to geolens-io/geolens. 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/geolens-io/geolens/main/AGENTS.mdgit clone --depth 1 https://github.com/geolens-io/geolensWrote 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/geolens-io/geolens/agents-md)<a href="https://agentmods.dev/instructions/geolens-io/geolens/agents-md"><img src="https://agentmods.dev/badge/instructions/geolens-io/geolens/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.03767 | $0.03767 |
| Opus 5 | $0.01884 | $0.01884 |
| Sonnet 5 | $0.00753 | $0.00753 |
| Haiku 4.5 | $0.00377 | $0.00377 |
Grade A, and why
geolens 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 today.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure
GeoLens mixes Python and TypeScript. Backend source is backend/app/: modules/ (domain areas), platform/ (shared services), processing/ (ingest/export/tiles), standards/ (OGC/STAC/DCAT), core/ (config, DB, permissions, edition). Migrations are in backend/alembic/, tests in backend/tests/. The React/Vite frontend is frontend/src/ (components/, pages/, hooks/, stores/, api/, i18n/, colocated __tests__/); Playwright specs are in e2e/. The CLI is cli/geolens_cli/, the read-only MCP server mcp/geolens_mcp/, generated SDKs sdks/, operations files scripts/, db/, .github/.
Architecture
Nginx (Vite proxy in dev) fronts the FastAPI api (catalog, search, OGC/STAC, vector tiles) and Titiler (COG raster tiles). A worker runs GDAL/ogr2ogr ingestion via the Procrastinate queue, which lives inside PostgreSQL. PostgreSQL 18 (PostGIS, pgvector, pg_trgm) is the single source of truth; MinIO/S3 holds objects; Valkey caches tiles and queries.
Backend: catalog is the core module (datasets/collections/records/features/maps/layers/search/sources/validation); access control is catalog/authorization.py. The datasets domain splits into api/ (routers) and domain/, where service_X sub-modules sit behind the façade domain/service.py. Import the façade, never a sub-module; backend/tests/test_layering.py enforces this and the other layer boundaries.
Frontend (React 19, @vis.gl/react-maplibre v8, maplibre-gl v6, TanStack Query, zustand, Tailwind): the map builder is builder/; every API call goes through apiFetch() in api/client.ts; the auth token lives in useAuthStore (persisted geolens-auth; outside React read useAuthStore.getState().token); reuse components/ui/.
SDKs are generated from backend/openapi.json with make sdks; never hand-edit generated files (only the auth.*, __init__ and index wrappers are hand-maintained). The CLI and MCP server are hand-maintained and wrap the SDK.
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.
- today Changed · -67 lines · -1,909 tokens per session fcb79e5b1029
- 2d ago Changed · +4 lines · +988 tokens per session b701aca037f1
- 8d ago First seen · 173 lines · 4,688 tokens per session scan A 58a66e0cf63c
geolens AGENTS.md is an instructions file published in the GitHub repository geolens-io/geolens (239 stars, last pushed today), licensed Apache-2.0. It adds 3,767 tokens to every session, about $0.0188 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-30.
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.