agentmods.dev

watch

A test watcher that reruns relevant software tests whenever source code, test files, or configuration changes.

In plain words
What is it for?
Use it to run all tests or a selected subset, rerun tests affected by changes, inspect failed tests, filter results, and update snapshots.
Why use it?
It shortens the feedback loop during development by showing whether recent edits caused failures.

Command

2 10mo ago A scan 10 tokens original MIT
View the source file cyperx84/claude-code-plugin-examples
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/cyperx84/claude-code-plugin-examples/watch
Clone the repo
git clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examples
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 383 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 $0.00010 $0.00383
Opus 5 $0.00005 $0.00192
Sonnet 5 $0.00002 $0.00077
Haiku 4.5 $0.00001 $0.00038

Measured yesterday against content hash 4fa98863b9db, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

examples/02-intermediate/testing-plugin/commands/watch.md · 67 lines

What it actually says

Test Watch Mode

Start test watch mode for: $ARGUMENTS (or all tests if not specified)

This starts an interactive watch session that:

  1. Initial test run:

    • Run all tests (or specified subset)
    • Show results

  2. Watch for changes:

    • Monitor source files
    • Monitor test files
    • Monitor configuration files

  3. Auto-rerun:

    • Run affected tests when files change
    • Show only changed test results
    • Maintain pass/fail history

  4. Interactive commands:

    • a - Run all tests
    • f - Run only failed tests
    • p - Filter by test name pattern
    • t - Filter by test file
    • q - Quit watch mode
    • c - Clear console
    • u - Update snapshots

  5. Smart features:

    • Only run tests for changed files
    • Show test execution time
    • Highlight regression (new failures)
    • Show coverage changes

Example output:

Watch mode started...

Watching: src/**/*.ts, tests/**/*.test.ts

✓ 142 tests passed (0 changed)
✗ 0 tests failed
⊘ 5 tests skipped

Coverage: 87.3% (no change)

Press a to run all tests.
Press f to run only failed tests.
Press q to quit watch mode.

File changed: src/utils/parser.ts
Running affected tests...

✓ parser.test.ts (12 tests, 324ms)

All tests passed!
Coverage: 87.5% (+0.2%)

Note: This runs in the background. Use BashOutput to check status.

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 · 67 lines · 10 tokens per session scan A 4fa98863b9db

Subscribe to this mod's changes

watch is a command published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 10 tokens to every session and 383 once invoked, about $0.0001 per session on Opus 5. 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-31.

Testing
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens