check

A command that checks whether a Rust codebase is ready to commit. It formats the code, runs static checks, executes tests, and fixes issues it finds.

In plain words
What is it for?
Use it to check formatting, compiler and lint warnings, and snapshot-based tests across a Rust workspace.
Why use it?
It gathers the main pre-commit checks in one operation instead of requiring you to run them separately.

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/tailcallhq/forgecode/check
Clone the repo
git clone --depth 1 https://github.com/tailcallhq/forgecode
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 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.00011 $0.00096
Opus 5 $0.00005 $0.00048
Sonnet 5 $0.00002 $0.00019
Haiku 4.5 $0.00001 $0.00010

Measured 2d ago 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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • check — 100% identical, 0 lines differ
.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. 2d ago 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 tailcallhq/forgecode (7,599 stars, last pushed 2d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.