check

A pre-commit check command for a Rust workspace and related project files. It runs formatting, compiler-style lint checks, tests, and a project-specific linter in sequence.

In plain words
What is it for?
Use it before committing to run cargo formatting, Clippy with warnings treated as errors, workspace tests, and the Poly linter; run hardening checks afterward when scanner, extraction, or indexing code changes.
Why use it?
It catches formatting problems, warnings, failing tests, and project rule violations before code is committed. Each check must pass before the next one runs, making failures easier to locate.

Command

Install

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.

agentmods
npx agentmods add commands/goldziher/basemind/check
Clone the repo
git clone --depth 1 https://github.com/Goldziher/basemind
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 178 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00010 $0.00178
Opus 5 $0.00005 $0.00089
Sonnet 5 $0.00002 $0.00036
Haiku 4.5 $0.00001 $0.00018

Measured 2d ago against content hash a45f69e58070, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check 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.

.ai-rulez/commands/check.md · 25 lines

What it actually says

Check

Run the commit triad. Use this before every commit.

  1. cargo fmt
  2. cargo clippy --workspace --all-targets --tests -- -D warnings
  3. cargo test --workspace
  4. poly lint .

Each step gates the next. On failure:

  • cargo fmt — re-stage formatted files.
  • clippy — fix or justify with a one-line // allow because… comment.
  • tests — diagnose the failure; never #[ignore] to bypass.
  • poly — fix per the poly-and-release-workflow skill.

After this passes, run /harden before pushing if the change touches the scanner / extract / index path.

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. 2d ago First seen · 25 lines · 10 tokens per session scan A a45f69e58070

Subscribe to this mod's changes

check is a command published in the GitHub repository Goldziher/basemind (91 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 178 once invoked, about $0.0001 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-30.