appydave-tools: Command for Claude Code

.claude/commands/cli-test.md

cli-test is a command for Claude Code from appydave/appydave-tools. It costs 0 tokens per session (1,601 once invoked), scanned A, original, MIT.

An automated tester for command-line features that runs commands and checks their results against project requirements.

In plain words
What is it for?
Use it to read acceptance criteria, design CLI integration tests, execute them, verify output, and write pass/fail reports.
Why use it?
It removes the need to rely on manual checks and records whether expected, error, and edge-case behavior passes.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is appydave/appydave-tools's own configuration. It tells Claude Code how to work on appydave-tools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything appydave-tools configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ruby bin/jump.rb list --format json; echo "Exit code: $?".

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/appydave/appydave-tools/main/.claude/commands/cli-test.md
Clone the repo
git clone --depth 1 https://github.com/appydave/appydave-tools

Made for: Claude Code.

Wrote 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.

agentmods badge for cli-test

README.md
[![agentmods](https://agentmods.dev/badge/commands/appydave/appydave-tools/cli-test.svg)](https://agentmods.dev/commands/appydave/appydave-tools/cli-test)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,601 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash e3e31edd3d8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.claude/commands/cli-test.md · 252 lines

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

  1. Read the spec and acceptance criteria
  2. Design a test suite covering all functionality
  3. Execute each test command
  4. Verify output matches expectations
  5. Record results in a test report
  6. 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:

  1. Run the command using Bash tool
  2. Capture output
  3. Verify against expected outcome
  4. 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

Read the full file on GitHub · 252 lines

Changes

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.

  1. yesterday First seen · 252 lines · 0 tokens per session scan A e3e31edd3d8b

Subscribe to this mod's changes

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.