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/navapbc/digital-service-orchestra/pythongit clone --depth 1 https://github.com/navapbc/digital-service-orchestraWhat 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.00058 | $0.00058 |
| Opus 5 | $0.00029 | $0.00029 |
| Sonnet 5 | $0.00012 | $0.00012 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
digital-service-orchestra python.instructions.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 2d 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
Python Coverage Areas
Coverage areas for Python:
- Subprocess and deserialization safety.
- File locking on shared-state writes.
- Dependency footprint — stdlib and existing
pyproject.tomldependencies are preferred over new packages.
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.
- 2d ago First seen · 13 lines · 58 tokens per session scan A 008363871f3c
digital-service-orchestra python.instructions.md is an instructions file published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 58 tokens to every session, about $0.0003 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
apm python.instructions.md
Python development guidelines.
programasweights-python AGENTS.md
Instructions for programasweights/programasweights-python, covering programasweights (paw), when to use paw, install, quickstart and compile your own from a description.
sports-skills CLAUDE.md
Instructions for machina-sports/sports-skills, covering claude.md - sports-skills guidelines, tech stack, commands and code conventions.
pysm AGENTS.md
Instructions for galsci/pysm, covering repository guidelines, project overview, project structure & key files, quick start commands and setup environment.
django-starter-template AGENTS.md
Instructions for wilfredinni/django-starter-template, covering agents.md, commands, lint & typecheck, architecture and testing.
foundry-local python-cffi-pointer-types.instructions.md
Use when working on the Python SDK's native bindings (cffi), especially when defining new Item subclasses, working with flItemQueue, or extending Request/Session methods that pass native handles.