Borrowing it
Nothing to install: this file belongs to HomenShum/NodeBenchAI. 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/HomenShum/NodeBenchAI/main/.claude/commands/nodebench-qa.mdgit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWrote 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/homenshum/nodebenchai/nodebench-qa)<a href="https://agentmods.dev/commands/homenshum/nodebenchai/nodebench-qa"><img src="https://agentmods.dev/badge/commands/homenshum/nodebenchai/nodebench-qa/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/homenshum/nodebenchai/nodebench-qa"><img src="https://agentmods.dev/badge/commands/homenshum/nodebenchai/nodebench-qa.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.00000 | $0.00301 |
| Opus 5.5 | $0.00000 | $0.00120 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
nodebench-qa 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
NodeBench QA Loop
Full QA loop: crawl → findings → fix suggestions → re-crawl → savings report.
Steps
-
Crawl the site Call
site_map({ url: '<target-url>' })to crawl all pages and get a session ID. -
Review findings Call
site_map({ session_id: '<id>', action: 'findings' })to see all QA issues. -
Generate test suggestions Call
suggest_tests({ session_id: '<id>' })to get scenario-based test cases. -
Fix issues For each finding, trace the root cause (5-whys) and apply minimal targeted fixes.
-
Re-crawl and diff Call
diff_crawl({ url: '<target-url>', baseline_id: '<original-session-id>' })to compare before/after. -
Report savings Call
compare_savings()to show token usage, time saved, and cost estimates.
Quick one-liner
If you have a running dev server:
site_map({ url: 'http://localhost:5191' })
Then follow the next suggestions in the response to drill down.
When to use
- After completing any implementation sprint
- Before any deploy or PR
- When the user says "QA", "check the site", "run quality checks"
- As part of the continuous flywheel loop
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 First seen · 40 lines · 0 tokens per session scan A cd68d5615ffd
nodebench-qa is a command published in the GitHub repository HomenShum/NodeBenchAI (15 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 301 tokens. 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
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
recette
Tests d'acceptance automatises avec Claude in Chrome.
lavra-qa
Browser-based QA verification of the running app -- systematic testing from the user's perspective.
test-browser
Run browser tests on pages affected by current PR or branch.
create-smoke-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ui-test.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.