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.

In plain words
What is it for?
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.
Why use it?
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.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/saagpatel/operant/agents-md
Clone the repo
git clone --depth 1 https://github.com/saagpatel/operant

Made for: Codex, OpenCode.

Per session 196 This file is loaded in full into every session.
When invoked 196 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00196 $0.00196
Opus 5 $0.00098 $0.00098
Sonnet 5 $0.00039 $0.00039
Haiku 4.5 $0.00020 $0.00020

Measured yesterday against content hash 4e59c27947d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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 · 29 lines

What it actually says

Portfolio Context

What This Project Is

operating-agent calibration benchmark with shipped public MCP access

Current State

Portfolio truth currently marks this project as active with boilerplate context. Phase 104 recovered minimum-viable context so future sessions can resume without rediscovery.

Stack

  • Stack still needs a deeper explicit handoff beyond this minimum context.

How To Run

  • Review the README and top-level scripts before the next session; this repo does not yet expose one canonical run command inside the new context block.

Known Risks

  • This repo only has minimum-viable recovery context today; deeper handoff details may still live in the README and supporting docs.

Use this context plus the README and supporting docs to resume the next active task, then promote the repo beyond minimum-viable by capturing a dedicated handoff, roadmap, or discovery artifact.

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.

  1. yesterday 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 196 tokens to every session, about $0.0010 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.