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/microsoft/agent-framework/pythongit clone --depth 1 https://github.com/microsoft/agent-frameworkWhat 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.00110 | $0.00110 |
| Opus 5 | $0.00055 | $0.00055 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
agent-framework 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 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
See AGENTS.md for project structure and package documentation.
Detailed conventions are in the agent skills under .github/skills/.
When changing the public root API surface (agent_framework/__init__.py), keep the lazy runtime export
registry, explicit runtime __all__, and agent_framework/__init__.pyi synchronized. Runtime deprecation
behavior for a public alias should live in the owning module, not as a special case in the root package.
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 · 11 lines · 110 tokens per session scan A 068a651b113f
agent-framework python.instructions.md is an instructions file published in the GitHub repository microsoft/agent-framework (13,222 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session, about $0.0006 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
harness-sdk AGENTS.md
AGENTS.md instructions for strands-agents/harness-sdk, covering agent development guide - strands agents monorepo, context, monorepo layout, where the "why" lives: team/ and writing code.
LeAgent AGENTS.md
Instructions for vixues/LeAgent, covering leagent development guidelines, project overview, architecture, execution topology (one kernel, many ingresses) and surface map (where things live).
pi-fabric AGENTS.md
Instructions for monotykamary/pi-fabric, covering agents.md, golden rule: build when done, before committing and commits.
swarmclaw CLAUDE.md
Instructions for swarmclawai/swarmclaw, covering claude.md, keeping instructions in sync, dev server, code quality and architecture.
semantix CLAUDE.md
Instructions for Gnosil/semantix, covering 项目规则（claude code） and 1. 改动须经用户过目；由 claude 提交到分支 + pr，用户 review 后合并.
kdcube AGENTS.md
Instructions for kdcube/kdcube, covering agents.md — operating rules for coding agents, shared ground rules (both classes), a. platform contributors, git and shared-tree etiquette and code architecture.