Borrowing it
Nothing to install: this file belongs to jnarowski/agentcmd. 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/jnarowski/agentcmd/main/.claude/commands/check.mdgit clone --depth 1 https://github.com/jnarowski/agentcmdWrote 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/jnarowski/agentcmd/check)<a href="https://agentmods.dev/commands/jnarowski/agentcmd/check"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/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/jnarowski/agentcmd/check"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/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.00009 | $0.00575 |
| Opus 5.5 | $0.00004 | $0.00230 |
| Sonnet 5.5 | $0.00002 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check
Reads the ## Validation section from README.md, runs the validation command, and reports all issues including errors and warnings. Does not make any fixes.
Variables
- $format: $1 (optional) - Output format: "text" or "json" (defaults to "text" if not provided)
Workflow
-
Read README.md
- Locate the
## Validationsection (search for exact header text) - Extract the command shown in the code block under this section
- If no command is found, report error and stop
- Locate the
-
Run Validation
- Execute the validation command using the Bash tool
- Capture the full output including errors, warnings, and info messages
- Do not attempt to fix any issues
-
Parse and Categorize Issues
- Analyze the output to identify all issues
- Group issues by type:
- Errors: Critical issues that prevent builds/tests from passing
- Warnings: Non-critical issues that should be addressed
- Info: Informational messages
- Count issues in each category
-
Report Results
- Display the validation command that was executed
- Show total counts by category (e.g., "5 errors, 3 warnings")
- Display the full validation output
- Summarize the validation status (pass/fail)
- If there are issues, suggest running
/fixto automatically resolve them
Report
JSON
IMPORTANT: If $format is "json", return raw JSON output (no ```json code fences, no markdown):
{
"success": true,
"validation_command": "bun run build && bun test",
"issues": {
"errors": 5,
"warnings": 3,
"info": 2
}
}
JSON Field Descriptions:
success: Always true if check command completed (even if validation failed)validation_command: The command that was executed from READMEissues.errors: Number of errors foundissues.warnings: Number of warnings foundissues.info: Number of info messages found
Text
Otherwise, provide this human-readable information to the user:
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 · 83 lines · 9 tokens per session scan A 716cd5e5a27a
check is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 575 once invoked, about $0.0000 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-09-01.
check compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| checkjnarowski/agentcmd | Command | 18 | 10mo ago | MIT | A | 9 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |