scopes: Command for Claude Code

.claude/commands/testing/run.md

run is a command for Claude Code from kamiazya/scopes. It costs 0 tokens per session (596 once invoked), scanned A, original, Apache-2.0.

A command that runs tests through the project's configured test runner. Tests are checks that verify whether code behaves as expected.

In plain words
What is it for?
It is for running the full test suite, a test file, a matching pattern, or a named test suite, then reporting the output and failures.
Why use it?
It gathers the test command and target from the project configuration, so you can run all tests or a selected part consistently.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

This is kamiazya/scopes's own configuration. It tells Claude Code how to work on scopes 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 scopes configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kamiazya/scopes. 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/kamiazya/scopes/main/.claude/commands/testing/run.md
Clone the repo
git clone --depth 1 https://github.com/kamiazya/scopes

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 run

README.md
[![agentmods](https://agentmods.dev/badge/commands/kamiazya/scopes/run/github.svg)](https://agentmods.dev/commands/kamiazya/scopes/run)
Your own site
<a href="https://agentmods.dev/commands/kamiazya/scopes/run"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/run/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.

agentmods 80×15 button for run

Your own site · 80×15
<a href="https://agentmods.dev/commands/kamiazya/scopes/run"><img src="https://agentmods.dev/badge/commands/kamiazya/scopes/run.svg" alt="Reviewed on agentmods" width="80" 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 596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00596
Opus 5.5 $0.00000 $0.00238
Sonnet 5.5 $0.00000 $0.00119
Haiku 4.5 $0.00000 $0.00060

Measured 2mo ago against content hash 5fe2ed591b89, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/commands/testing/run.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run Tests

Execute tests with the configured test-runner agent.

Usage

/testing:run [test_target]

Where test_target can be:

  • Empty (run all tests)
  • Test file path
  • Test pattern
  • Test suite name

Quick Check

# Check if testing is configured
test -f .claude/testing-config.md || echo "❌ Testing not configured. Run /testing:prime first"

If test target provided, verify it exists:

# For file targets
test -f "$ARGUMENTS" || echo "⚠️ Test file not found: $ARGUMENTS"

Instructions

1. Determine Test Command

Based on testing-config.md and target:

  • No arguments → Run full test suite from config
  • File path → Run specific test file
  • Pattern → Run tests matching pattern

2. Execute Tests

Use the test-runner agent from .claude/agents/test-runner.md:

Execute tests for: $ARGUMENTS (or "all" if empty)

Requirements:
- Run with verbose output for debugging
- No mocks - use real services
- Capture full output including stack traces
- If test fails, check test structure before assuming code issue

3. Monitor Execution

  • Show test progress
  • Capture stdout and stderr
  • Note execution time

4. Report Results

Success:

✅ All tests passed ({count} tests in {time}s)

Failure:

❌ Test failures: {failed_count} of {total_count}

{test_name} - {file}:{line}
  Error: {error_message}
  Likely: {test issue | code issue}
  Fix: {suggestion}

Run with more detail: /testing:run {specific_test}

Mixed:

Tests complete: {passed} passed, {failed} failed, {skipped} skipped

Failed:
- {test_1}: {brief_reason}
- {test_2}: {brief_reason}

5. Cleanup

# Kill any hanging test processes
pkill -f "jest|mocha|pytest" 2>/dev/null || true

Error Handling

  • Test command fails → "❌ Test execution failed: {error}. Check test framework is installed."
  • Timeout → Kill process and report: "❌ Tests timed out after {time}s"
  • No tests found → "❌ No tests found matching: $ARGUMENTS"

Read the full file on GitHub · 109 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. 2mo ago First seen · 109 lines · 0 tokens per session scan A 5fe2ed591b89

Subscribe to this mod's changes

run is a command published in the GitHub repository kamiazya/scopes (2 stars, last pushed 11mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 596 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-31.

Related

run compared with commands from other repositories

run next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
runkamiazya/scopesCommand211mo agoApache-2.0A0Claude Code
diagnose-deeptracezscaler/zscaler-mcp-serverCommand5510d agoMITA29Claude Code
troubleshoot-experiencezscaler/zscaler-mcp-serverCommand5510d agoMITA25Claude Code
app-healthzscaler/zscaler-mcp-serverCommand5510d agoMITA16Claude Code
compare-locationszscaler/zscaler-mcp-serverCommand5510d agoMITA20Claude Code
investigate-alertszscaler/zscaler-mcp-serverCommand5510d agoMITA23Claude Code
investigate-sandboxzscaler/zscaler-mcp-serverCommand5510d agoMITA30Claude Code