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/draincoder/pyproject/agents-mdgit clone --depth 1 https://github.com/draincoder/pyprojectWhat 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.00369 | $0.00369 |
| Opus 5 | $0.00185 | $0.00185 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
pyproject 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
Project Structure
config/
docker/
src/
domain/
application/
infrastructure/
presentation/
tests/
unit/
integration/
e2e/
Rules:
- Dependencies flow inward: presentation → application → domain
domaincontains only business logic, no external dependenciesinfrastructureimplements interfaces defined inapplication
Architecture Principles (if applicable)
- Follow Clean Architecture by default
- Depend on abstractions, not concrete implementations
- Extend behavior via composition, not modification
- Keep modules small with a single responsibility
Tooling & Standards (Mandatory)
- Python 3.14
- Task runner:
just - Formatting & linting: Ruff
- Type checking: mypy
- Testing: pytest with coverage
- All code must be fully type annotated
Common commands:
just install
just lint
just test
just run
just up
just down
Testing Rules (Mandatory)
- Tests mirror
src/structure - Use
unit/,integration/,e2e/ - Use Arrange / Act / Assert with explicit comments
- Do not add comments in tests except parametrization case descriptions
- Name tests by behavior and expected outcome
- Prefer unit tests; add integration tests when behavior spans layers
- Keep tests deterministic, fast, and isolated from network/IO
Commit & Pull Request Rules
- Use Conventional Commits (e.g.
feat: add auth middleware) - PRs must include a concise description and motivation
Local Configuration
Before running locally:
cp config/template.config.yaml config/config.yaml
cp config/template.env config/.env
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 · 80 lines · 369 tokens per session scan A 34dd2a0d2b44
pyproject AGENTS.md is an instructions file published in the GitHub repository draincoder/pyproject (5 stars, last pushed 1mo ago), licensed MIT. It adds 369 tokens to every session, about $0.0018 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
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.
buildNext
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).
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.
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).
spec-kit 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.
langchain 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.