Borrowing it
Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. 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/TheAstrelo/Claude-Pipeline/main/.claude/commands/qb.mdgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/theastrelo/claude-pipeline/qb)<a href="https://agentmods.dev/commands/theastrelo/claude-pipeline/qb"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/qb/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/theastrelo/claude-pipeline/qb"><img src="https://agentmods.dev/badge/commands/theastrelo/claude-pipeline/qb.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.00364 |
| Opus 5.5 | $0.00000 | $0.00146 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
qb 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
Behavior validation - verify tests pass and outputs match design.
Purpose
Verify that implemented code behaves correctly:
- Build succeeds
- Tests pass
- Behavior matches design specifications
- Edge cases from critique are handled
Execution
Use the quality-behavior agent.
Input:
build-report.md— What was builtdesign.md— Expected behaviorcritique.md— Edge cases to verify
Process:
- Run build:
npm run build - Run tests:
npm test(if tests exist) - Verify specifications:
- Check behavior against design.md requirements
- Verify edge cases from critique.md are handled
- Append results to
qa-report.md
Verification Matrix
| Requirement | How to Verify |
|---|---|
| API returns X | Check response shape |
| Handles empty data | Check code path |
| Auth required | Check middleware |
| Multi-tenant | Check user_id filter |
Output
After validation, report:
## Quality Behavior Complete
**Verdict:** [PASS | FAIL]
### Build
- Status: [PASS | FAIL]
- Warnings: [N]
### Tests
- Status: [PASS | FAIL | NO_TESTS]
- Passed: [N]
- Failed: [N]
### Specification Compliance
[Table of requirements and verification status]
### Edge Cases
[Table of edge cases and handling status]
### Issues Found
[List of behavioral issues]
### Next Step
Run `/qd` for documentation check.
Gate
This command is part of the QA pipeline.
Order: /denoise → /qf → /qb → /qd → /security-review
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 · 0 tokens per session scan A 81f19abc736a
qb is a command published in the GitHub repository TheAstrelo/Claude-Pipeline (47 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 364 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
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.
ccc-audit
Audit the current project for dependency vulnerabilities, oversized bundles, type errors, dead code, hardcoded secrets, undocumented env vars and a missing CLAUDE.md. Use when you want a health score before a release or review.
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
claude-loop
Use a fresh headless Claude session (Fable by default) as an independent reviewer of the whole repo, area by area (or of one branch's diff with --base), fix every real finding with regression tests, and loop until each area comes back clean twice in a row. The /codex-loop pattern on Anthropic usage. Runs autonomously.
p6-func-regression
Ensures that existing functionality has not been broken by new changes.
unity-test
Writes missing tests and runs them via MCP. Identifies untested code, creates EditMode/PlayMode tests, executes via runtests, reports results.