Borrowing it
Nothing to install: this file belongs to Benkapner/claude-code-basecamp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Benkapner/claude-code-basecamp/main/.claude/commands/check-code.mdgit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWrote 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.
[](https://agentmods.dev/commands/benkapner/claude-code-basecamp/check-code)<a href="https://agentmods.dev/commands/benkapner/claude-code-basecamp/check-code"><img src="https://agentmods.dev/badge/commands/benkapner/claude-code-basecamp/check-code/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/benkapner/claude-code-basecamp/check-code"><img src="https://agentmods.dev/badge/commands/benkapner/claude-code-basecamp/check-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.00231 |
| Opus 5.5 | $0.00010 | $0.00092 |
| Sonnet 5.5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
check-code 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 1mo 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.
What it actually says
Check Code (lightweight)
Look at the Python code in the current directory or the path provided by the user. This is the fast feedback command; use /verify for the complete check.
Run these checks:
- Run
ruff check .to find linting issues - Run
ruff format --check .to check formatting - Run
mypy . --ignore-missing-importsfor type checking - Run
pytest --cov -qto check test coverage
For each check, report:
- What passed
- What failed
- How to fix the failures
If all checks pass, tell the user the code looks good.
If there are failures, prioritize them:
- Security issues first
- Type errors second
- Lint issues third
- Formatting last
Also check if functions are too long (over 50 lines) and if there's code duplication.
At the end, give an overall verdict: READY or NEEDS WORK.
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.
- 1mo ago Changed · +18 tokens per session a43557925fe9
- 1mo ago First seen · 31 lines · 7 tokens per session scan A 2af096cb0abc
check-code is a command published in the GitHub repository Benkapner/claude-code-basecamp (18 stars, last pushed 28d ago), licensed MIT. It adds 25 tokens to every session and 231 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
test-cases
Use when writing test cases, generating tests, supplementing test coverage, or improving test completeness — auto-scans project, designs multi-dimensional test cases with coverage matrix.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
complete
Complete a partially implemented feature by filling gaps and ensuring production readiness.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
rclone_test_changenotify
Log any change notify requests for the remote passed in.
sdd-implement
Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.