bazel-mcp: Instructions file for Codex

AGENTS.md

bazel-mcp AGENTS.md is an instructions file for Codex, OpenCode from ewhauser/bazel-mcp. It costs 351 tokens per session, scanned A, original, MIT.

Repository instructions for a local service that lets an agent request Bazel builds and inspections through a controlled interface. Bazel is a build system, and MCP is the tool protocol used by the service.

In plain words
What is it for?
Use them when changing or testing the Bazel MCP service, reviewing its three exposed operations, updating fixtures, running approved checks, or investigating performance and workflow issues caused by the service.
Why use it?
They preserve rules needed for safe, predictable build requests, including protocol-only output, secret redaction, deterministic results, and bounded evidence. They also define the required checks and dependency boundaries.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex.

This is ewhauser/bazel-mcp's own configuration. It tells Codex and OpenCode how to work on bazel-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bazel-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ewhauser/bazel-mcp. 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/ewhauser/bazel-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ewhauser/bazel-mcp

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.

agentmods badge for bazel-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ewhauser/bazel-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/ewhauser/bazel-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ewhauser/bazel-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ewhauser/bazel-mcp/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.

agentmods 80×15 button for bazel-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ewhauser/bazel-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ewhauser/bazel-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 351 This file is loaded in full into every session.
When invoked 351 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00351 $0.00351
Opus 5.5 $0.00140 $0.00140
Sonnet 5.5 $0.00070 $0.00070
Haiku 4.5 $0.00035 $0.00035

Measured 2mo ago against content hash 61651901751f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bazel-mcp 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 2mo 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 · 30 lines

What it actually says

Agent instructions

This repository implements a token-efficient, local Bazel MCP invocation service. Preserve these invariants:

  • The server exposes exactly bazel.run, bazel.inspect, and bazel.cancel.
  • MCP stdout is protocol-only; tracing and diagnostics go to stderr.
  • Never invoke Bazel through a shell or concatenate request arguments.
  • Preserve raw evidence locally while enforcing model-visible byte budgets.
  • Keep the crate dependency direction in specification 002. Only the server depends on rmcp; the production store is database-free filesystem storage.
  • Keep reducers deterministic. Fixture updates require reviewed golden diffs.
  • Redact secrets before summaries, durable metadata, and telemetry.

Use make build, make test, make check, make test-bazel-matrix, make fuzz-smoke, and the explicit token benchmark targets. Do not run the long Abseil benchmark as an ordinary unit test. Use Conventional Commits; Release Please owns versions and the changelog.

Always use the Bazel MCP tools instead of invoking Bazel or Bazelisk directly. When using Bazel MCP reveals a performance issue, bug, or agent-workflow inefficiency caused by MCP behavior, create or update the repository-root LEARNINGS.md. Record the concrete MCP symptom, its impact on tool calls or model-visible tokens when applicable, an actionable follow-up, and the Codex Thread ID where the observation occurred. Agent-workflow observations are especially valuable when they expose inefficient protocol behavior, result reduction, or inspection flows. Do not add general project, Bazel, CI, release, or unrelated workflow learnings. Do not record secrets or raw sensitive output.

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. 2mo ago First seen · 30 lines · 351 tokens per session scan A 61651901751f

Subscribe to this mod's changes

bazel-mcp AGENTS.md is an instructions file published in the GitHub repository ewhauser/bazel-mcp (10 stars, last pushed 6d ago), licensed MIT. It adds 351 tokens to every session, about $0.0014 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.

Related

bazel-mcp AGENTS.md compared with instructions from other repositories

bazel-mcp AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
bazel-mcp AGENTS.mdewhauser/bazel-mcpInstructions file106d agoMITA351Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
vscode ai-customization.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA1,907GitHub Copilot