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/ebhattad/nfl-mcp/agents-mdgit clone --depth 1 https://github.com/ebhattad/nfl-mcpWrote 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/ebhattad/nfl-mcp/agents-md)<a href="https://agentmods.dev/instructions/ebhattad/nfl-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ebhattad/nfl-mcp/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.01572 | $0.01572 |
| Opus 5 | $0.00786 | $0.00786 |
| Sonnet 5 | $0.00314 | $0.00314 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
nfl-mcp 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 4d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents working on this codebase.
What This Project Is
nfl-mcp is a local MCP server that ingests NFL data from nflreadpy into a DuckDB database and exposes it to AI clients (Claude Desktop, VS Code) via the Model Context Protocol. All data lives in a single ~/.nfl-mcp/nflread.duckdb file. No network calls happen at query time — only at ingest time.
Repository Layout
nfl_mcp/
cli.py # Click CLI: serve, ingest, init, setup-client, doctor
server.py # MCP server: TOOLS list + _DISPATCH + call_tool handler
tools.py # Tool implementations (nfl_schema, nfl_status, nfl_query, ...)
schema_pbp.py # PBP schema strings (_SCHEMA_SUMMARY, _SCHEMA_CATEGORIES) — pure data, no logic
ingest.py # Data ingestion: run_ingest_datasets, idempotency, schema reconciliation
registry.py # Declarative dataset definitions (REGISTRY, DatasetDef)
database.py # get_db_connection() context manager (read-only DuckDB)
config.py # ~/.nfl-mcp/config.json read/write, get_duckdb_path()
tests/
test_registry.py # Registry structure, coverage windows, loader functions
test_ingest.py # Ingest helpers using in-memory DuckDB (no network)
test_cli.py # CLI commands using click.testing.CliRunner
test_tools.py # Tool functions — unit + integration (require_db fixture)
test_safety.py # SQL injection / forbidden keyword guardrails
Key Architectural Rules
Adding a new MCP tool requires changes in exactly two files:
tools.py— implement the function, add to__all__server.py— add aTool(...)entry toTOOLSand an entry to_DISPATCH
Adding a new dataset requires changes in exactly one file:
registry.py— add aDatasetDefentry toREGISTRY
The ingest loop in ingest.py is fully generic — it reads from the registry and handles everything else (idempotency, schema reconciliation, bulk vs ranged mode).
Never hardcode table schemas for non-pbp tables. Use nfl_schema(table=<name>) which queries information_schema.columns at runtime. PBP schema strings live in schema_pbp.py because they carry human-readable annotations — not just types.
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.
- 4d ago First seen · 122 lines · 1,572 tokens per session scan A 1eb666a2cda3
nfl-mcp AGENTS.md is an instructions file published in the GitHub repository ebhattad/nfl-mcp (8 stars, last pushed 1mo ago), licensed MIT. It adds 1,572 tokens to every session, about $0.0079 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.