What is operant AGENTS.md?

Repository instructions for the Operant project, an operating-agent calibration benchmark with public MCP access. They summarize the project's current status, limited setup information, risks, and suggested next step.

Use them when starting work on Operant, reviewing its current portfolio status, checking how it can be run, or deciding what project documentation should be added next.

They give a future contributor enough context to resume work without rediscovering the project's basic purpose and state. They also make clear where the handoff is still incomplete.

How saagpatel/operant configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to saagpatel/operant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/saagpatel/operant/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/saagpatel/operant

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/saagpatel/operant/agents-md/github.svg)](https://agentmods.dev/instructions/saagpatel/operant/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/saagpatel/operant/agents-md"><img src="https://agentmods.dev/badge/instructions/saagpatel/operant/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/saagpatel/operant/agents-md"><img src="https://agentmods.dev/badge/instructions/saagpatel/operant/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 491 This file is loaded in full into every session.

When invoked 491 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00491	$0.00491
Opus 5.5	$0.00196	$0.00196
Sonnet 5.5	$0.00098	$0.00098
Haiku 4.5	$0.00049	$0.00049

Measured 23d ago against content hash bfda36154826, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

operant 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 23d 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.

AGENTS.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

OPERANT is an operating-agent calibration benchmark with public MCP access. The root scripts score and validate benchmark runs; operant_lab/ contains the self-serve runner and local lab utilities.

Layout

operant*.json, generated/, and operant_templates.json: benchmark inputs and generated case data.
operant_lab/, root *.py, and examples/: scoring, execution, lab tools, and fixtures.
lab/public/: sanitized public artifacts. Private run data stays under lab/runs/ and results/.
mcp/: read-only MCP server, scripts, tests, and generated corpus/manifest.
docs/: benchmark policy, evidence limits, and operating guidance.

Setup

Install uv 0.13.x and use Python 3.12 or newer. The repository's preferred Python patch is in .python-version. Install Node.js from .node-version with its bundled npm version, then run make check from the repository root.

Checks

make check runs the frozen Python environment, compile and unit checks, evaluation-split verification and Ruff lint, locked MCP install, generated-file checks, typecheck, Vitest, CLI build and probe, manifest verification, and package parity. It does not dispatch paid providers.

Boundaries

score_orchestration.py and score_orchestration_judge.py are hash-bound.
lab/public/ and mcp/src/*.generated.ts are generated or hash-bound public evidence; preserve their bytes unless the task explicitly governs regeneration.
lab/ private run data and results/ are user data. Do not read, overwrite, publish, or remove them without a task that requires it.
Provider dispatch can incur cost. Keep routine checks offline; a paid dispatch is optional and requires explicit task authority.
Do not publish, release, or deploy unless the task explicitly requests it.

Delivery

Keep changes scoped to the requested outcome. Run the narrowest relevant checks and make check when the task requires the full contract. Report actual results and distinguish local checks from provider, production, or human acceptance. Preserve unrelated changes and use small conventional commits when committing is part of the task.

Read the full file on GitHub · 49 lines

Changes

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.

23d ago Changed · +20 lines · +290 tokens per session bfda36154826
1mo ago Changed · +5 tokens per session c9ef7230c3ea
2mo ago First seen · 29 lines · 196 tokens per session scan A 4e59c27947d4

Subscribe to this mod's changes

operant AGENTS.md is an instructions file published in the GitHub repository saagpatel/operant (0 stars, last pushed 2d ago), licensed MIT. It adds 491 tokens to every session, about $0.0020 per session on Opus 5.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.

AI Safety Finance and fintech Prompt Injection Python agent-evaluation ai-agents llm-benchmark

operant AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
operant AGENTS.mdsaagpatel/operant	Instructions file	0	2d ago	MIT	A	491	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

operant: Instructions file for Codex