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/yerjosh/operatorengine/agents-mdgit clone --depth 1 https://github.com/yerjosh/operatorENGINEWrote 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/yerjosh/operatorengine/agents-md)<a href="https://agentmods.dev/instructions/yerjosh/operatorengine/agents-md"><img src="https://agentmods.dev/badge/instructions/yerjosh/operatorengine/agents-md.svg" alt="Measured on agentmods" 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.00279 | $0.00279 |
| Opus 5 | $0.00139 | $0.00139 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
operatorENGINE 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 5d 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:
- operatorENGINE CLAUDE.md — 91% identical, 2 lines differ
What it actually says
Instructions for AI coding agents (Codex and others)
This repository is a blueprint: the human you're working with is a non-technical business owner, and your job is to build their CRM from the specification in this repo.
Do this now:
- Read
BUILD_INSTRUCTIONS.mdin full. It contains the complete specification: interaction rules, tech stack, database schema, API contracts, build phases with acceptance criteria, and security requirements. - If
BUILD_LOG.mdexists, read it — a previous session already started; resume from the last completed phase. - Otherwise, start with Phase 0.
Standing rules (also in the spec — they always apply):
- Secrets go in
.envonly. Never commit them, never print them, never write them into any tracked file. Verify.gitignorebefore every commit. - Work one phase at a time; demonstrate each phase's acceptance criteria before moving on.
- Ask for API keys only when the current phase needs them, and point the human to
docs/GETTING-YOUR-KEYS.mdfor how to obtain each one. - Explain your work in plain business English.
- Keep
BUILD_LOG.mdupdated after every phase so any future session can resume.
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.
- 5d ago First seen · 18 lines · 279 tokens per session scan A 5cb017f388bc
operatorENGINE AGENTS.md is an instructions file published in the GitHub repository yerjosh/operatorENGINE (5 stars, last pushed 1mo ago), licensed MIT. It adds 279 tokens to every session, about $0.0014 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
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).
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.
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.
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).