Borrowing it
Nothing to install: this file belongs to untra/operator. 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/untra/operator/main/AGENTS.mdgit clone --depth 1 https://github.com/untra/operatorWrote 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/untra/operator/agents-md)<a href="https://agentmods.dev/instructions/untra/operator/agents-md"><img src="https://agentmods.dev/badge/instructions/untra/operator/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/untra/operator/agents-md"><img src="https://agentmods.dev/badge/instructions/untra/operator/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.04082 | $0.04082 |
| Opus 5.5 | $0.01633 | $0.01633 |
| Sonnet 5.5 | $0.00816 | $0.00816 |
| Haiku 4.5 | $0.00408 | $0.00408 |
Grade A, and why
operator 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 16d 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.
How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - operator
Project Overview
operator is a Rust TUI application for orchestrating Claude/Codex/Gemini/Grok CLI agents across multi-project codebases. It manages ticket queues, launches agents, tracks progress, and provides notifications.
Tech Stack
- Language: Rust (core), TypeScript (
ui/,webcomponents/,vscode-extension/) - TUI: ratatui (crossterm backend); tokio async runtime
- Server surfaces: axum REST API + utoipa OpenAPI (
src/rest/), MCP server (src/mcp/), ACP (src/acp/) - Web: Vite/React SPA in
ui/, sharedwebcomponents/package, thin VS Code extension webview - Notifications: mac-notification-sys (macOS), notify-rust (Linux), webhooks
- Config: config crate (TOML); File Watching: notify crate
Code Style
Aim for functional software development with a focus on stateless, single responsibility testable functions.
Minimize use of comments entirely; they should be terse and used judiciously, ideally one line tops.
Data types come from rust; typescript and docs binds are generated from low-level rust types annotated with comments that embed as descriptions into configuration and reference files.
Favor falsey defaults ; lets aim not to enforce default=true or some other javascript-truthy default value.
Comments
Code comments are terse, short and punctual. Comments should not refer to implementation or current wip status.
Plans & Specs Location
Write superpowers plans to superpowers/plans/ and design specs to superpowers/specs/ (repo root, not hosted).
Development Standards
- Ask, don't assume. If something is unclear, ask before writing into a corner. Never make silent assumptions about intent, architecture or requirements.
- Consider the simplest solution first. First attempt the simplest approach that could work, then consider abstractions and flexibility with regards to similar implementations.
- Avoid changing unrelated code. If a file or function is not part of the current task, do not modify it.
- Flag uncertainty explicitly. If you are not confident about an approach or technical detail, say so before proceeding.
- I am open to ideas on better approaches or strategies. Speak up and suggest a better course if I am off-course from a better solution.
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.
- 16d ago Changed · +1 lines · +19 tokens per session d03a8cc097f9
- 26d ago First seen · 323 lines · 4,063 tokens per session scan A 99cd2a67a4c8
operator AGENTS.md is an instructions file published in the GitHub repository untra/operator (41 stars, last pushed 6d ago), licensed MIT. It adds 4,082 tokens to every session, about $0.0163 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-10-02.
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).
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.