Borrowing it
Nothing to install: this file belongs to gura105/operational-ontology. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gura105/operational-ontology/main/AGENTS.mdgit clone --depth 1 https://github.com/gura105/operational-ontologyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/gura105/operational-ontology/agents-md)<a href="https://agentmods.dev/instructions/gura105/operational-ontology/agents-md"><img src="https://agentmods.dev/badge/instructions/gura105/operational-ontology/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/gura105/operational-ontology/agents-md"><img src="https://agentmods.dev/badge/instructions/gura105/operational-ontology/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00747 | $0.00747 |
| Opus 5 | $0.00374 | $0.00374 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
operational-ontology 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository workflow
This is a small, readable reference implementation of Operational Ontology. Keep the runtime and examples easy to read; prefer focused changes over new abstractions. README explains the concept; IMPLEMENTATION explains runtime contracts.
Development
maincontains the published application;nextcollects work for the next release. Keepmainas the default branch for readers.- Start ordinary work from the latest
origin/next, on a separate branch. Targetnextexplicitly when creating a PR (gh pr create --base next). - Keep commits focused. Update affected examples, tests, and both language versions of documentation with API changes.
- Run
pnpm typecheck,pnpm test, andpnpm demobefore merging changes. CI must pass. - Merging an ordinary PR does not request a release. Do not bump the version, create a version tag, or publish a Release for each PR.
- Do not push directly to, delete, or force-push
mainornext. Do not bypass or weaken repository rules to complete a task. trafficholds repository traffic snapshots written weekly by theTrafficworkflow, which needs theTRAFFIC_TOKENsecret (a fine-grained personal access token limited to this repository withAdministration: Read-only). Do not rebase, rewrite, or deletetraffic.
Release
-
When a release is requested, prepare its version in
package.jsonthrough a PR tonext. Summarize changes since the previous published version, including API migration, in the release PR description. Package version changes belong to release preparation, not ordinary feature PRs. -
Open the release PR from this repository's
nexttomain. Use a merge commit (gh pr merge --merge), preserving the shared branch history. Wait for CI. -
After merging, run the
Releaseworkflow onmain. Supply the version withoutv, the exact 40-character main commit, and the prepared release notes. Run withdry_run=truefirst, thenfalseto publish. For example:gh workflow run release.yml --ref main -f version=0.5.0 -f commit=MAIN_COMMIT_SHA -F notes=@/path/to/release-notes.md -f dry_run=true
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.
- today Changed · +1 lines · +57 tokens per session c4925314d6e6
- yesterday First seen · 37 lines · 690 tokens per session scan A eeeeaa4c20e5
operational-ontology AGENTS.md is an instructions file published in the GitHub repository gura105/operational-ontology (86 stars, last pushed today), licensed MIT. It adds 747 tokens to every session, about $0.0037 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-09-13.
Other instructions, from other repositories
next.js AGENTS.md
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 buildNext.instructions.md
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).
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.
langchain AGENTS.md
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.
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
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.