Borrowing it
Nothing to install: this file belongs to developerz-ai/universal-lsp. 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/developerz-ai/universal-lsp/main/.claude/commands/check.mdgit clone --depth 1 https://github.com/developerz-ai/universal-lspWrote 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/developerz-ai/universal-lsp/check)<a href="https://agentmods.dev/commands/developerz-ai/universal-lsp/check"><img src="https://agentmods.dev/badge/commands/developerz-ai/universal-lsp/check/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/developerz-ai/universal-lsp/check"><img src="https://agentmods.dev/badge/commands/developerz-ai/universal-lsp/check.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.00014 | $0.00189 |
| Opus 5.5 | $0.00006 | $0.00076 |
| Sonnet 5.5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
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 2mo 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
bin/check --changed- If it passes and you are about to push:
bin/check(background if slow).
Stop at the first failure, fix it, re-run only that command.
Report one line per step: ✓ <label> or ✗ <label> — <error summary>.
Fix rules:
- Compiler warning → fix the code. Never add a suppression;
-Werroris on deliberately. - Guard violation → the message names the fix. Never an allowlist entry.
- Format →
bin/fmt. - Test failure → read the assertion before touching anything. Do not "fix" a test to match new behaviour unless the new behaviour is what was asked for.
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.
- 2mo ago First seen · 22 lines · 14 tokens per session scan A 9a72b222d366
check is a command published in the GitHub repository developerz-ai/universal-lsp (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 189 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-31.
Other commands, from other repositories
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
coverage
Ingest or inspect test-coverage reports (LCOV, Cobertura, Clover, Go cover profiles, JaCoCo, Salesforce Apex JSON, or repowise JSON; a coverage.py .coverage builds the per-test map only), or gate a change on its patch coverage in CI.
impacted-tests
Print the tests whose coverage intersects a change's changed lines — for a commit, base..head range, or staged diff.
check
Run the local lint + test triad before committing.
test
Verify the requested repository surface without unnecessary rebuilds.
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.