Borrowing it
Nothing to install: this file belongs to r3tr0eth/emap-labs. 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/r3tr0eth/emap-labs/main/CLAUDE.mdgit clone --depth 1 https://github.com/r3tr0eth/emap-labsWrote 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/r3tr0eth/emap-labs/claude-md)<a href="https://agentmods.dev/instructions/r3tr0eth/emap-labs/claude-md"><img src="https://agentmods.dev/badge/instructions/r3tr0eth/emap-labs/claude-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.00958 | $0.00958 |
| Opus 5 | $0.00479 | $0.00479 |
| Sonnet 5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
emap-labs CLAUDE.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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — emap-labs
Capa de datos e inteligencia detrás de emap (github.com/r3tr0eth/emap-labs,
público). Roadmap: docs/ROADMAP.md. Reglas duras: docs/ETICA-DATOS.md
(infraestructura jamás personas) y la regla financiera: emap solo gasta
dinero que emap trae.
Relación con otros repos
../emap-next: producto en producción (Vercel + VPS Hetzner). Sin remoto git — solo commits locales; deploy convercel deploy --prod --yes.- Los pipelines de
datasets/escriben enemap-next/data/processed/y se registran en su manifest (python -m data_catalog validate|quality|checkcon el venv de emap-next).
Comandos
../emap-next/.venv/bin/python evals/run.py [--retriever baseline|semantic|hybrid] \
[--lang es|eu] [--split dev|heldout|all] [--min-pass N] # evals
./evals/sync-data.sh # refrescar snapshot para CI tras cambiar datos
../emap-next/.venv/bin/python datasets/<pipeline>/build.py # pipelines
./service/deploy.sh # desplegar servicio semántico al VPS
ssh [email protected] # VPS (OTP :8082, semantic :8083, nginx)
- Venv propio (
.venv, python3.13: fastembed/numpy) solo para el retriever semántico; todo lo demás usa el venv de emap-next. - held-out (
ho-*) jamás se usa para calibrar; si se mira para depurar, se promociona a dev y se escriben casos nuevos. - CI corre en cada push (
.github/workflows/evals.yml) con gates --min-pass; si tocas retriever o corpus, actualiza los umbrales conscientemente en el mismo PR, nunca para "que pase".
Loops (convención de trabajo con Claude Code)
Regla previa: lo determinista va en scripts (cron del VPS o *.sh del
repo), los bucles de agente son para juicio e iteración. Recetas:
- Turn-based + verificación: cualquier cambio de retriever/corpus termina
con
evals/run.pyen dev (ES y EU) antes de commitear; cambios de UI en emap-next, con la skillverify-frontend-change/ QA CDP. /goalcon gate de eval (el mejor encaje: criterio determinista):/goal sube hybrid held-out EU a ≥75% sin bajar ES de 79% ni dev, máx 5 intentos— tocando solo dev para iterar; held-out se corre UNA vez al final./looppara CI: tras push con cambios de evals,/loop 5m mira el workflow evals de emap-labs y arregla si falla.- Proactivo (pendiente de activar, consume cuota — decidir Gaizka):
rutina semanal sobre este repo: re-ejecutar pipelines con fetch remoto
(neighborhoods/Overpass),
sync-data.sh, evals completas, y abrir issue si hay drift de datos o caída de gates. Solo tiene sentido semanal — las fuentes no cambian más rápido.
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.
- 7d ago First seen · 65 lines · 958 tokens per session scan A e66476896126
emap-labs CLAUDE.md is an instructions file published in the GitHub repository r3tr0eth/emap-labs (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 958 tokens to every session, about $0.0048 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
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.