check

A command that runs the project’s formatting, tests, API checks, linting, and selected interface tests before a commit.

In plain words
What is it for?
Running Rust formatting checks, PoolAI’s `cargo test-ci`, the OpenAPI gap audit after API changes, optional Clippy checks, and UI end-to-end tests.
Why use it?
It finds build, style, API, or end-to-end test failures before changes are committed or shared.

Command for Cursor

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/platinoff/poolai/check
Clone the repo
git clone --depth 1 https://github.com/platinoff/poolAI

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 184 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.00000 $0.00184
Opus 5 $0.00000 $0.00092
Sonnet 5 $0.00000 $0.00037
Haiku 4.5 $0.00000 $0.00018

Measured yesterday against content hash 457e0bb713bb, 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.

.cursor/commands/check.md · 20 lines

What it actually says

Check Command

Run comprehensive code checks before committing (MSYS2 bash).

export PATH="$HOME/.cargo/bin:/ucrt64/bin:/usr/bin:$PATH"
export K8S_OPENAPI_ENABLED_VERSION=1.28
cd /s/rust/poolAI

Recommended sequence:

  1. cargo fmt --all --check (or cargo fmt --all to fix)
  2. cargo test-ci (канон PoolAI; .cargo/config.toml)
  3. After API changes: cargo run --bin poolai-openapi-gap-audit (expect 0 missing)
  4. Optional: cargo clippy --all-targets --all-features (CI parity)
  5. After src/ui/ or e2e/: cd e2e && npm run test:ci

Return summary of results.

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 · 20 lines · 0 tokens per session scan A 457e0bb713bb

Subscribe to this mod's changes

check is a command published in the GitHub repository platinoff/poolAI (4 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 184 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.