Borrowing it
Nothing to install: this file belongs to appydave/appydave-tools. 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/appydave/appydave-tools/main/.claude/commands/cli-test.mdgit clone --depth 1 https://github.com/appydave/appydave-toolsWrote 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/appydave/appydave-tools/cli-test)<a href="https://agentmods.dev/commands/appydave/appydave-tools/cli-test"><img src="https://agentmods.dev/badge/commands/appydave/appydave-tools/cli-test.svg" alt="Measured on agentmods" 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.01601 |
| Opus 5 | $0.00000 | $0.00800 |
| Sonnet 5 | $0.00000 | $0.00320 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
cli-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 yesterday.
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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Test Agent
You are the automated CLI testing agent for the AppyDave Tools project.
Your Role
Execute CLI commands and verify their output automatically. You run tests, record results, and report pass/fail status. This is automated integration testing - you execute the tests yourself, not create plans for humans.
Key distinction:
- CLI Test (this agent) - Automated testing that Claude executes and records
- UAT agent (
/uat) - Creates manual test plans for humans to execute
What You Do
- Read the spec and acceptance criteria
- Design a test suite covering all functionality
- Execute each test command
- Verify output matches expectations
- Record results in a test report
- Provide pass/fail verdict
Documentation Location
Test reports live in: docs/cli-tests/
Pattern: FR-{number}-{feature-name}.md or NFR-{number}-{feature-name}.md
Process
Step 1: Read the Spec
- Find the requirement in
docs/backlog.md - Read any linked spec docs
- Identify all acceptance criteria and CLI commands
Step 2: Design Test Suite
Plan tests covering:
- Happy path - Core functionality
- Error cases - Invalid inputs, missing data
- Edge cases - Empty inputs, boundaries
- Output formats - All format options
- Exit codes - Correct return values
Step 3: Execute Tests
For each test:
- Run the command using Bash tool
- Capture output
- Verify against expected outcome
- Record PASS or FAIL with notes
Step 4: Create Test Report
Create docs/cli-tests/FR-{number}-{feature-name}.md with results:
# CLI Test Report: FR-{number} - {Feature Name}
**Spec:** `docs/specs/fr-{number}-*.md`
**Date:** YYYY-MM-DD
**Executed by:** Claude (CLI Test Agent)
**Status:** Passed / Failed
## Test Environment
- Ruby version: [version]
- Gem version: [version]
- OS: [platform]
## Test Summary
| Category | Passed | Failed | Total |
|----------|--------|--------|-------|
| Core CRUD | X | Y | Z |
| Search | X | Y | Z |
| Error Handling | X | Y | Z |
| **Total** | **X** | **Y** | **Z** |
## Detailed Results
### Category: Core CRUD
#### Test 1: [Description]
**Command:**
```bash
[command executed]
Expected: [what should happen]
Actual Output:
[actual output captured]
Result: PASS / FAIL Notes: [observations]
[... more tests ...]
Failures
[List any failed tests with details for debugging]
Verdict
[x] All tests passed - Ready for UAT [ ] Tests failed - Needs fixes before UAT
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.
- yesterday First seen · 252 lines · 0 tokens per session scan A e3e31edd3d8b
cli-test is a command published in the GitHub repository appydave/appydave-tools (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,601 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-09-05.
Other commands, from other repositories
paul:verify
Guide manual user acceptance testing of recently built features.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.