Borrowing it
Nothing to install: this file belongs to TheK3nsai/ops-brain. 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/TheK3nsai/ops-brain/main/CLAUDE.mdgit clone --depth 1 https://github.com/TheK3nsai/ops-brainWrote 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/thek3nsai/ops-brain/claude-md)<a href="https://agentmods.dev/instructions/thek3nsai/ops-brain/claude-md"><img src="https://agentmods.dev/badge/instructions/thek3nsai/ops-brain/claude-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.02710 | $0.02710 |
| Opus 5 | $0.01355 | $0.01355 |
| Sonnet 5 | $0.00542 | $0.00542 |
| Haiku 4.5 | $0.00271 | $0.00271 |
Grade A, and why
ops-brain CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Prod does not publish `localhost:3000` on the host** — `docker-compose.prod.yml` attaches `ops-brain` to Docker networks for the reverse proxy; it does not expose `ports:`. Verify readiness with `docker compose -f do How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ops-brain
Rust MCP server for cross-agent coordination. Rust 2021, rmcp 1.6, PostgreSQL 18 via sqlx, stdio/HTTP transport.
Scope: a small team bus. The MCP surface is handoffs, bounded knowledge, and check-in; machine ingestion, wake polling, and stateless briefings use narrow REST endpoints. Inventory, incidents, monitoring, and ticketing are out of scope by design (ROADMAP.md).
For roadmap philosophy + hard stops (what we will/won't build, and why), see ROADMAP.md. For shipped history, see CHANGELOG.md.
Surface (15 tools)
- Knowledge (4):
add_knowledge,update_knowledge,delete_knowledge,search_bus(knowledge by default; optional handoff search; empty/*browse) - Handoffs (8):
create_handoff(optionalin_reply_to),get_handoff(exact full UUID),accept_handoff,complete_handoff(optionalcommit_hash),list_handoffs,delete_handoff,list_replies_to_me,mark_merged(flip tostatus=merged, recordmerge_commit+merged_at) - Team bus (1):
check_in— open action handoffs (pending + accepted) + recent notify-class handoffs foragent_name - Online peers (2):
list_live_peers,send_live_message— ephemeral online-only routing through the packaged Claude Channel and Codex App Server adapters; never queued or persisted.
REST-only (no MCP tools, zero agent token cost): POST /api/handoff, GET /api/pending, and POST /api/briefing. The first two serve machine-filed handoffs and wake polling through scoped machine tokens (OPS_BRAIN_MACHINE_TOKENS); briefings are stateless delivery output for the main bearer. GET /health is liveness; GET /ready checks PostgreSQL readiness. Producer contract in docs/machine-callers.md. Recurrence/dead-man stay on producers' own schedulers — ops-brain never owns execution timing.
Operator maintenance: ops-brain backfill-embeddings [--table knowledge|handoffs] [--batch-size N] replaces the former agent-visible backfill tool.
Identity: interactive sessions authenticate with per-agent tokens (OPS_BRAIN_AGENT_TOKENS) that bind from_agent server-side — MCP write tools reject mismatching identity and /live uses the binding as peer provenance. Agent tokens reach /mcp and /live, never REST. The main bearer stays unbound as operator break-glass and cannot register a live peer. Contract in docs/agent-tokens.md.
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.
- yesterday Changed · -4 lines · -89 tokens per session 6c49fedecefa
- 6d ago First seen · 97 lines · 2,799 tokens per session scan A bfafd97b0068
ops-brain CLAUDE.md is an instructions file published in the GitHub repository TheK3nsai/ops-brain (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,710 tokens to every session, about $0.0136 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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.
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).
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).
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.
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.