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 rules/baz-scm/baz-plugin/baz-codebase-explorationgit clone --depth 1 https://github.com/baz-scm/baz-pluginWhat 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.02175 | $0.02175 |
| Opus 5 | $0.01087 | $0.01087 |
| Sonnet 5 | $0.00435 | $0.00435 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
baz-codebase-exploration 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 2d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Baz Codebase Exploration
This rule applies when planning a change across your org's repos. It applies whether or not the relevant repos are cloned locally — and especially when a change crosses a contract boundary between repos: you edit one side, another repo defines the other. Baz MCP tools replace gh / glab for code search. Use gh / glab only to read a specific file once you already know its path.
When this rule fires
- The user asks to plan a feature, scope a change, or design an implementation
- The change might touch more than one repository in the org
- You own one side of a cross-repo contract (API param, request/response schema, event payload) — even when that side is checked out locally
- The relevant code lives in repos the user has not cloned locally
Tool routing — strict
| Job | Tool |
|---|---|
| Find which repos are involved | repo_search (Baz) |
| Find code by symbol / regex inside a repo | remote_grep (Baz) |
| Find files by name / glob inside a repo | remote_file_search (Baz) |
| Read a specific file you already know the path of | gh api repos/<owner>/<repo>/contents/<path> |
Forbidden — these are the patterns that cause the most waste:
- Do not call
gh api repos/<owner>/<repo>/git/trees/HEAD?recursive=1. Useremote_file_searchinstead. - Do not call
gh search code. Useremote_grepinstead. - Do not call
remote_file_searchand thengh api .../git/treesfor the same directory. Pick one — and the answer is alwaysremote_file_search. - Do not call
gh api .../contents/<dir>to walk a directory. That's a search; useremote_file_search.
Recommended flow
Step 1: Orient (once)
If the user has not told you which repo(s) to look in, call repo_search exactly once with broad keywords:
repo_search(keywords: ["<topic>", "<topic synonym>"], domains?: ["API", "BUSINESS_LOGIC", ...])
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.
- 2d ago First seen · 112 lines · 2,175 tokens per session scan A 64879809db23
baz-codebase-exploration is a cursor rule published in the GitHub repository baz-scm/baz-plugin (10 stars, last pushed 5d ago), licensed MIT. It adds 2,175 tokens to every session, about $0.0109 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 cursor rules, from other repositories
archcore-context
Archcore knowledge base context — document types, MCP tools, and conventions for working with .archcore/ documents.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
rendering-and-memoization
React anti-patterns R9, R11, R12 — index-as-key in dynamic lists, context overuse for frequent updates, inline functions breaking memoization. Load on a review hit for any of these codes, or when tuning render performance.
pn-plugin-quality-gates
Keep Cursor plugin manifests, paths, and component metadata valid during plugin authoring.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.