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/johnthagen/python-blueprint/agents-mdgit clone --depth 1 https://github.com/johnthagen/python-blueprintWhat 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.00071 | $0.00071 |
| Opus 5 | $0.00036 | $0.00036 |
| Sonnet 5 | $0.00014 | $0.00014 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
python-blueprint 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
Repository Guidelines
General Instructions
- ALWAYS format the code via
uv run nox --session fmtAFTER you're done with your task - ALWAYS check for lint errors via
uv run nox --session lintand fix them - ALWAYS check for type errors via
uv run nox --session type_checkand fix them
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 · 8 lines · 71 tokens per session scan A 539fb5ade5cc
python-blueprint AGENTS.md is an instructions file published in the GitHub repository johnthagen/python-blueprint (738 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session, about $0.0004 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
temple8 AGENTS.md
Instructions for nullhack/temple8, covering agents.md, binding constraints, driving a state, parsimony and workflow.
specleft CLAUDE.md
Instructions for SpecLeft/specleft, covering specleft for ai agents, tl;dr for agents, when to use specleft (critical), agent rationale and what specleft is (agent view).
autoharness AGENTS.md
Instructions for tigerless-labs/autoharness: This repo uses Open Knowledge — collaborative markdown via MCP. .open-knowledge/config.yml (with optional /.open-knowledge/config.yml; CLI/env may override) is the path contract: content.dir is the root for relative paths; content.include lists globs that add markdown…
python-cheatsheet copilot-instructions.md
Copilot instructions for labex-labs/python-cheatsheet, covering python cheatsheet - ai coding assistant instructions, project overview, architecture & key patterns, content structure and routing & layout system.
ZipAgent AGENTS.md
Instructions for JiayuXu0/ZipAgent, covering repository guidelines, project structure & module organization, build, test & development commands, coding style & naming conventions and testing guidelines.
medusa CLAUDE.md
Claude Code instructions for Pantheon-Security/medusa, covering medusa - medusa security scanning, critical: release gate — do not skip, 4. security hardening tests (must show: all pass), critical: bash sandbox and project overview.