check

A command that runs formatting, code checks, and tests to see whether a Rust project is ready to commit.

In plain words
What is it for?
Formatting Rust code, running Clippy checks, executing snapshot tests, and removing or updating unused test snapshots.
Why use it?
It catches code-quality and test problems before changes are committed, and instructs the agent to fix them.

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/justrach/codegraff2/check
Clone the repo
git clone --depth 1 https://github.com/justrach/codegraff2
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 96 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00011 $0.00096
Opus 5 $0.00005 $0.00048
Sonnet 5 $0.00002 $0.00019
Haiku 4.5 $0.00001 $0.00010

Measured yesterday against content hash 27689fa5bb2e, 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 yesterday.

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.

Origin

This is a copy

100% identical to check — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.forge/commands/check.md · 10 lines

What it actually says

  • Run the lint and test commands and verify if everything is fine. cargo +nightly fmt --all; cargo +nightly clippy --fix --allow-staged --allow-dirty --workspace cargo insta test --accept --unreferenced=delete
  • Fix every issue found in the process
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. yesterday First seen · 10 lines · 11 tokens per session scan A 27689fa5bb2e

Subscribe to this mod's changes

check is a command published in the GitHub repository justrach/codegraff2 (24 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 96 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to check, differing in 0 lines, and is treated as a copy.