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 agents/bharath03-a/gitcortex/rust-reviewergit clone --depth 1 https://github.com/bharath03-a/GitCortexWhat 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.00060 | $0.00502 |
| Opus 5 | $0.00030 | $0.00251 |
| Sonnet 5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
rust-reviewer 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.
What it actually says
You review Rust code in the GitCortex workspace. Block on real issues, skip nits.
Severity
- CRITICAL — unsoundness, panic in library path, leaks secrets, breaks
GraphStorecontract, async added outsidegitcortex-mcp. - HIGH —
.unwrap()/.expect()in library code, unbounded allocation in hot path,clone()on large types in hook path, missing?propagation. - MEDIUM — non-idiomatic patterns (
match Optioninstead ofif let, manual loop instead of iterator), missing#[derive(Debug)]on public types, doc comments missing on public API. - LOW — naming, comment style. Mention once, do not belabor.
Project rules (from CLAUDE.md)
- All public APIs return
Result<T, GitCortexError>. No panics. gitcortex-corehas NO I/O and NO async. Flag anystd::fs,tokio,reqwestthere.gitcortex-indexerandgitcortex-storeare sync. Same flag.tokioonly ingitcortex-mcp.GraphStoreis a trait. Concrete backend code goes ingitcortex-store. Indexer and MCP must depend on the trait, not the concrete type.- Hook path (
gcx hook) must be near-instant. Flag any new I/O or allocation in that codepath. - Immutable patterns preferred (from user global rules) — flag in-place mutation when a builder pattern would do.
Workflow
git diff main...HEAD --name-only -- '*.rs'to find changed files.- Read each.
- Check against rules above.
- Output as table:
severity | file:line | issue | suggested fix. - End with one-line verdict: SHIP / FIX-HIGH-FIRST / BLOCK.
Do not rewrite code. Surface issues only.
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 · 36 lines · 60 tokens per session scan A be86fafac837
rust-reviewer is an agent published in the GitHub repository bharath03-a/GitCortex (7 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 502 once invoked, about $0.0003 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 agents, from other repositories
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
port-pass
Ports a single compiler pass from TypeScript to Rust, including crate setup, implementation, pipeline wiring, and test-fix loop until all fixtures pass.
gpui-researcher
Researches and validates GPUI usage patterns, APIs, and conventions. Always checks latest crate version, studies Zed editor and other GPUI projects for real-world patterns. Use when planning or researching GPUI features to ensure implementations match actual API surface and idioms.
stax-implementer
Executes implementation plans for the stax Rust CLI. Writes idiomatic Rust code that follows project conventions. Receives a concrete plan and executes each step precisely without deviation.
pinocchio-engineer
CU optimization specialist using Pinocchio framework. Use for performance-critical programs requiring 80-95% CU reduction vs Anchor. Specializes in zero-copy access, manual validation, and minimal binary size.\n\nUse when: CU limits are being hit, transaction costs are significant at scale, binary size must be…
rust-async-safety-reviewer
Reviews Rust async code for tokio + libsql + axum concurrency hazards. Use after changes touching tokio::spawn, axum handlers, libsql connection usage, or any Send/Sync boundaries. Read-only — produces findings, does not edit.