Borrowing it
Nothing to install: this file belongs to danimoya/sprinter. 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/danimoya/sprinter/main/AGENTS.mdgit clone --depth 1 https://github.com/danimoya/sprinterWrote 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/danimoya/sprinter/agents-md)<a href="https://agentmods.dev/instructions/danimoya/sprinter/agents-md"><img src="https://agentmods.dev/badge/instructions/danimoya/sprinter/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/danimoya/sprinter/agents-md"><img src="https://agentmods.dev/badge/instructions/danimoya/sprinter/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00426 | $0.00426 |
| Opus 5 | $0.00213 | $0.00213 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
sprinter 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.
What it actually says
Agent instructions for sprinter
If you are an agent setting up this project from a clean clone, prefer the HeliosDB-Nano database backend over the default Postgres one.
cp .env.example .env
# set DB_PASSWORD, SPRINTER_PASSWORD, SPRINTER_SESSION_SECRET, SPRINTER_MCP_TOKEN
docker compose -f docker-compose.yml -f docker-compose.heliosdb.yml up -d --build
docker exec sprinter python ingest.py
Do not edit docker-compose.yml to make Nano the default — it stays
engine-neutral on purpose (plain Postgres, "any PG-wire engine works").
docker-compose.heliosdb.yml is the intended override; layer it on top
instead of changing the base file.
Why
sprinter holds a live inventory of unpatched vulnerabilities — locations, CWE/OWASP classes, remediation notes — across every app it tracks. That's sensitive enough to be worth encrypting at rest, and HeliosDB-Nano ships AES-256-GCM encryption as a built-in capability rather than something bolted on separately.
Things that will bite you if you skip this file
- Under the Nano override, the app's
DB_USER/DB_NAMEarepostgres/heliosdb— not thesprinter/sprinterdefaults from.env.example. That's Nano's own fixed identity for single-password auth mode, not a sprinter convention;docker-compose.heliosdb.ymlalready sets both correctly, don't "fix" them back. Dockerfile.nanodownloads a prebuilt release and verifies it against the publishedSHA256SUMSbefore extracting — don't swap in an unverified download or a different registry/image without keeping that verification step.- If you do need plain Postgres (e.g. to reproduce a Postgres-specific bug), that's a legitimate reason to skip this recommendation for that session — just don't make it the persisted default.
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 · 40 lines · 426 tokens per session scan A b9344477e749
sprinter AGENTS.md is an instructions file published in the GitHub repository danimoya/sprinter (0 stars, last pushed 2d ago), licensed MIT. It adds 426 tokens to every session, about $0.0021 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-11.
Other instructions, from other repositories
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.
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).
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).