Borrowing it
Nothing to install: this file belongs to damiansire/web-vaccine-tracker. 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/damiansire/web-vaccine-tracker/main/AGENTS.mdgit clone --depth 1 https://github.com/damiansire/web-vaccine-trackerWrote 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/damiansire/web-vaccine-tracker/agents-md)<a href="https://agentmods.dev/instructions/damiansire/web-vaccine-tracker/agents-md"><img src="https://agentmods.dev/badge/instructions/damiansire/web-vaccine-tracker/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.00517 | $0.00517 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
web-vaccine-tracker 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 8d 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.
What it actually says
AGENTS.md
Guía para cualquier agente (o humano) que abra este repo. La barra de
calidad completa vive en CLAUDE.md — no la dupliques acá,
léela antes de tocar código. Esto es el checklist operativo.
Checklist pre-PR (numerado, en orden)
npm run verifyen verde (lint + test + build) — es literalmente el mismo comando que corre CI.- Si tocaste dominio/lógica (no solo estilos/copy), agregá o actualizá un test que lo cubra.
- Si tomaste una decisión no obvia (elegiste A sobre B, descartaste un
hallazgo, te desviaste del patrón existente), dejá una línea en
_audits/DECISIONES.mdcon el porqué. - Si agregaste una regla nueva de arquitectura/stack, reflejala en
CLAUDE.md— no dejes la barra desactualizada respecto al código real. - Verificá visualmente en el navegador cualquier cambio de UI antes de darlo por terminado (no alcanza con "compila y los tests pasan").
STOP-signs (parar y preguntar, no improvisar)
- Nunca
git pushni ninguna operación de escritura a GitHub sin pedido explícito — el dueño del repo lo hace a mano. - Nunca agregar una segunda librería de UI/estilos (el repo anterior
tenía cuatro sistemas de estilo compitiendo — ver
CLAUDE.md). - Nunca volver a
echarts-for-react; el wrapper propio (src/components/EChart.tsx) existe porque ese paquete tiene un bug real de interop con Vite (ver_audits/DECISIONES.md). - Nunca hacer fetch en runtime al dataset de OWID — el dominio está
cerrado, el dataset se hornea a build-time (
npm run generate:data) y se versiona junto al código. - Si un cambio requiere instalar una dependencia nueva, pará y justificá
por qué el problema no se resuelve con lo que ya está — el patrón de este
repo es preferir código chico propio sobre una dependencia (ver el
wrapper de EChart, o
assertLastDataRowsen vez de Zod).
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.
- 8d ago First seen · 37 lines · 517 tokens per session scan A d6517ef28ab0
web-vaccine-tracker AGENTS.md is an instructions file published in the GitHub repository damiansire/web-vaccine-tracker (23 stars, last pushed 1mo ago), licensed MIT. It adds 517 tokens to every session, about $0.0026 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.