check

A project-checking command that reviews recent work against the codebase's architecture rules and runs the project's checks. It also removes unnecessary logs, comments, and leftovers from discarded approaches.

In plain words
What is it for?
Use it at the end of a development task to verify architecture compliance, run `bun run check:all`, and fix any reported errors.
Why use it?
It catches implementation and quality problems before the work is considered finished and keeps temporary debugging changes out of the codebase.

Command for Claude Code

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

Made for: Claude Code.

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 133 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.00133
Opus 5 $0.00005 $0.00067
Sonnet 5 $0.00002 $0.00027
Haiku 4.5 $0.00001 $0.00013

Measured 3d ago against content hash 2f21e41919b9, 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 3d 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.

.claude/commands/check.md · 23 lines

What it actually says

/check - Check Work

Purpose

Check work for adherance with architecture and run checks

Usage

/check

Execution

  1. Check all work in this session for adherance with docs/developer/architecture-guide.md.
  2. Remove any unnececarry comments or console.logs we've introduced and clean up any "leftovers" from approaches we tried but didn't work.
  3. Run bun run check:all and fix any errors.
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. 3d ago First seen · 23 lines · 10 tokens per session scan A 2f21e41919b9

Subscribe to this mod's changes

check is a command published in the GitHub repository coollabsio/jean (1,250 stars, last pushed 8d ago), licensed Apache-2.0. It adds 10 tokens to every session and 133 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.