Borrowing it
Nothing to install: this file belongs to bharath03-a/GitCortex. 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/bharath03-a/GitCortex/main/.claude/commands/dev/rust-precommit.mdgit clone --depth 1 https://github.com/bharath03-a/GitCortexWrote 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/commands/bharath03-a/gitcortex/rust-precommit)<a href="https://agentmods.dev/commands/bharath03-a/gitcortex/rust-precommit"><img src="https://agentmods.dev/badge/commands/bharath03-a/gitcortex/rust-precommit/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.
<a href="https://agentmods.dev/commands/bharath03-a/gitcortex/rust-precommit"><img src="https://agentmods.dev/badge/commands/bharath03-a/gitcortex/rust-precommit.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00210 |
| Opus 5.5 | $0.00000 | $0.00084 |
| Sonnet 5.5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
rust-precommit 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.
What it actually says
Run the GitCortex pre-commit gate in parallel and report results.
Execute these checks (parallelise where independent):
cargo fmt --all -- --check— formatting driftcargo clippy --workspace --all-targets -- -D warnings— lintscargo nextest run --workspace— tests (falls back tocargo test --workspaceif nextest absent)cargo check -p gitcortex-mcp— verifies viz/dist embed works (requirescd viz && npm run buildto have run at least once)
If any step fails:
- Surface the first failure verbatim.
- Offer to launch the rust-build-fixer subagent for fmt/clippy/build issues, or the rust-reviewer subagent for clippy lints requiring judgement.
If all pass, print: READY TO COMMIT and a one-line summary of what was checked.
Do not commit anything. This command is a gate, not an action.
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.
- 2mo ago First seen · 17 lines · 0 tokens per session scan A 98b326572cd4
rust-precommit is a command published in the GitHub repository bharath03-a/GitCortex (8 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 210 tokens. 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 commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.