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/blueflyio/openstandardagents/agents-mdgit clone --depth 1 https://github.com/blueflyio/openstandardagentsWhat 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
openstandardagents 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.
What it actually says
Dev environment tips
- Review the OSSA manifest for tool configurations
- Ensure all required dependencies are installed
- Configure environment variables as needed
Testing instructions
- Run all tests before committing:
npm test - Ensure code coverage meets project standards
- Validate against OSSA schema:
ossa validate manifest.yaml
PR instructions
- Follow conventional commit format
- Include tests for new features
- Update documentation as needed
- Ensure CI passes before requesting review
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 · 24 lines · 123 tokens per session scan A c1904f663b45
openstandardagents AGENTS.md is an instructions file published in the GitHub repository blueflyio/openstandardagents (5 stars, last pushed 15d ago), licensed Apache-2.0. 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-31.
Other instructions, from other repositories
caplets AGENTS.md
Instructions for spiritledsoftware/caplets, covering agents.md, commands, package map, agent skills and issue tracker.
gram AGENTS.md
AGENTS.md instructions for speakeasy-api/gram, a project described as: Securely scale AI usage across your organization. A single stack to Connect, Secure, Observe and Distribute agents, MCPs, and Skills within your company.
gram GEMINI.md
Gemini CLI instructions for speakeasy-api/gram, a project described as: Securely scale AI usage across your organization. A single stack to Connect, Secure, Observe and Distribute agents, MCPs, and Skills within your company.
gram CLAUDE.md
Claude Code instructions for speakeasy-api/gram, covering gram project structure guide, customer data is confidential, key directories, server and client/dashboard.
AutoAgents AGENTS.md
Instructions for liquidos-ai/AutoAgents, covering autoagents repository guidelines, project structure & module organization, code quality, naming conventions and error handling.
claude-code-karma CLAUDE.md
Instructions for JayantDevkar/claude-code-karma, covering claude.md, project overview, quick start, clone (no submodule init needed — this is a monorepo) and start api (terminal 1).