Borrowing it
Nothing to install: this file belongs to AssafWoo/homebrew-pandafilter. 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/AssafWoo/homebrew-pandafilter/main/.claude/commands/test.mdgit clone --depth 1 https://github.com/AssafWoo/homebrew-pandafilterWrote 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/assafwoo/homebrew-pandafilter/test)<a href="https://agentmods.dev/commands/assafwoo/homebrew-pandafilter/test"><img src="https://agentmods.dev/badge/commands/assafwoo/homebrew-pandafilter/test/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/assafwoo/homebrew-pandafilter/test"><img src="https://agentmods.dev/badge/commands/assafwoo/homebrew-pandafilter/test.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.00450 |
| Opus 5 | $0.00000 | $0.00225 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
test 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 9d 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
Run full test suite
Run all PandaFilter verification steps in order. Stop and report on first failure. This is the required pre-commit gate.
Steps
Step 1 — Workspace unit + integration tests
cargo test --workspace 2>&1
Pass: zero failures (exit code 0).
Step 2 — Handler benchmarks
cargo test -p panda handler_benchmarks -- --nocapture 2>&1
Pass: zero failures. Output should show savings > 0% for all known handlers.
Step 3 — Fixture savings check (no API key needed)
cargo run -p panda-eval -- --savings-only 2>&1
Pass: exit code 0, recall ≥ 80% across fixtures.
Step 4 — Repo benchmark (29 commands, 4 repos)
python3 ccr-eval/benchmarks/run_benchmark.py --after-only 2>&1
Pass: Weighted savings line in the output shows ≥ 40%.
How to run
Execute each step above, capturing output. After each step:
- If exit code ≠ 0 → print the failing output and stop with "BLOCKED: Step N failed."
- If Step 4's weighted savings drops below 40% → stop with "BLOCKED: savings regression."
After all steps pass, print a summary table:
Step 1 — cargo test --workspace PASS
Step 2 — handler_benchmarks PASS
Step 3 — panda-eval --savings-only PASS
Step 4 — repo benchmark PASS (weighted savings: XX.X%)
All checks passed. Safe to commit.
Notes
- Step 4 requires the benchmark repos to exist under
ccr-eval/benchmarks/repos/. If repos are missing, skip Step 4 and warn the user. - All steps should be run from the workspace root (
/Users/assafpetronio/Desktop/ccr). - Do not run with
--release; debug builds are the pre-commit target.
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.
- 9d ago First seen · 54 lines · 0 tokens per session scan A d44d3ecd7d17
test is a command published in the GitHub repository AssafWoo/homebrew-pandafilter (100 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 450 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
test
A command for running a project's automated tests, which are checks that software behaves as expected. It detects common project types and chooses a matching test command.
qa
A quality-assurance testing agent that checks whether software meets its stated acceptance requirements. It tests normal use, edge cases, failures, and regressions, then classifies the problems it finds.
verify
A command that runs a project's main quality checks in sequence: build, type checking, linting, tests, security scanning, and Git status checks. Linting checks code style and common mistakes; Git tracks file changes.
review
Verify the build matched the plan. Automated checks + walkthrough with you.
test
Generate tests for completed phase code. Detects test framework and targets key files.
validate-phase
Post-build quality gate. Identifies test gaps and spawns nyquist-auditor to fill them.