check

check is a command for coding agents from davepoon/buildwithclaude. It costs 9 tokens per session (371 once invoked), scanned A, original, MIT.

A project-checking command that runs the validation tools defined by a project and fixes the errors they report without committing changes.

In plain words
What is it for?
It is for detecting the package manager, finding check or test scripts, running suitable checks for several languages, fixing failures, and rerunning validation.
Why use it?
It helps restore a passing project check while leaving version history and version numbers unchanged.

Command

Part of the all-commands plugin — 23 commands shipped together

About the project

davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.

davepoon/buildwithclaude · 3,415 stars · on GitHub · buildwithclaude.com

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

Or install all-commands, the plugin that ships this one along with the rest of its 23 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for check

README.md
[![agentmods](https://agentmods.dev/badge/commands/davepoon/buildwithclaude/check.svg)](https://agentmods.dev/commands/davepoon/buildwithclaude/check)
Your own site
<a href="https://agentmods.dev/commands/davepoon/buildwithclaude/check"><img src="https://agentmods.dev/badge/commands/davepoon/buildwithclaude/check.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 371 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.1 $0.00009 $0.00371
Opus 5 $0.00005 $0.00186
Sonnet 5 $0.00002 $0.00074
Haiku 4.5 $0.00001 $0.00037

Measured today against content hash 6abd601f0cf4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 today.

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.

plugins/all-commands/commands/check.md · 44 lines

What it actually says

Run project validation checks and resolve any errors found.

Process:

  1. Detect Package Manager (for JavaScript/TypeScript projects):

    • npm: Look for package-lock.json
    • pnpm: Look for pnpm-lock.yaml
    • yarn: Look for yarn.lock
    • bun: Look for bun.lockb
  2. Check Available Scripts:

    • Read package.json to find check/validation scripts
    • Common script names: check, validate, verify, test, lint
  3. Run Appropriate Check Command:

    • JavaScript/TypeScript:

      • npm: npm run check or npm test
      • pnpm: pnpm check or pnpm test
      • yarn: yarn check or yarn test
      • bun: bun check or bun test
    • Other languages:

      • Python: pytest, flake8, mypy, or make check
      • Go: go test ./... or golangci-lint run
      • Rust: cargo check or cargo test
      • Ruby: rubocop or rake test
  4. Fix Any Errors:

    • Analyze error output
    • Fix code issues, syntax errors, or test failures
    • Re-run checks after fixing
  5. Important Constraints:

    • DO NOT commit any code
    • DO NOT change version numbers
    • Only fix errors to make checks pass

If no check script exists, run the most appropriate validation for the project type.

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. today First seen · 44 lines · 9 tokens per session scan A 6abd601f0cf4

Subscribe to this mod's changes

check is a command published in the GitHub repository davepoon/buildwithclaude (3,415 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 371 once invoked, about $0.0000 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-09-05.