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/stephenleo/openmicro/agents-mdgit clone --depth 1 https://github.com/stephenleo/OpenMicroWhat 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.00123 | $0.00123 |
| Opus 5 | $0.00062 | $0.00062 |
| Sonnet 5 | $0.00025 | $0.00025 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
OpenMicro 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- OpenMicro CLAUDE.md — 100% identical, 0 lines differ
What it actually says
OpenMicro — project conventions
Releases
- Release inside the parent PR: when a fix/feature PR is going to ship as a release, push the version bump (
npm version X.Y.Z --no-git-tag-version) and CHANGELOG entry as a commit on that same PR — do not open a separate release PR. After the parent PR merges, tagvX.Y.Zon main and push the tag; the publish workflow handles npm. - Verification gate before any release commit:
npm run typecheck && npm run lint && npm run format:check && npm test.
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 · 7 lines · 123 tokens per session scan A 6c2f9e84309c
OpenMicro AGENTS.md is an instructions file published in the GitHub repository stephenleo/OpenMicro (127 stars, last pushed 10d ago), licensed MIT. It adds 123 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
apm changelog.instructions.md
Changelog format and conventions based on Keep a Changelog.
ai-driven-development AGENTS.md
Instructions for CodeAlive-AI/ai-driven-development, covering ai-driven development — development guide, git publishing defaults, when to create tags and releases, requires a new tag/release and does not require a new tag/release.
codemap CLAUDE.md
Instructions for JordanCoin/codemap, covering 🛑 stop — run codemap before any task, repo root requirement (critical) and required usage.
azure-sdk-for-rust changelog.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
kmux AGENTS.md
Instructions for kkd927/kmux, covering agents.md, kmux focus and test discipline.