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.
npx agentmods add instructions/ewhauser/bazel-mcp/agents-mdgit clone --depth 1 https://github.com/ewhauser/bazel-mcpWhat 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 | $0.00351 | $0.00351 |
| Opus 5 | $0.00176 | $0.00176 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
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 3d 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.
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, andbazel.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.
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.
- 3d ago First seen · 30 lines · 351 tokens per session scan A 61651901751f
bazel-mcp AGENTS.md is an instructions file published in the GitHub repository ewhauser/bazel-mcp (10 stars, last pushed 21d ago), licensed MIT. It adds 351 tokens to every session, about $0.0018 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.
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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.