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.
npx agentmods add commands/superclaude-org/superclaude_framework/testgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWhat 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 | $0.00011 | $0.00640 |
| Opus 5 | $0.00005 | $0.00320 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test — 95% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:test - Testing and Quality Assurance
Triggers
- Test execution requests for unit, integration, or e2e tests
- Coverage analysis and quality gate validation needs
- Continuous testing and watch mode scenarios
- Test failure analysis and debugging requirements
Usage
/sc:test [target] [--type unit|integration|e2e|all] [--coverage] [--watch] [--fix]
Behavioral Flow
- Discover: Categorize available tests using runner patterns and conventions
- Configure: Set up appropriate test environment and execution parameters
- Execute: Run tests with monitoring and real-time progress tracking
- Analyze: Generate coverage reports and failure diagnostics
- Report: Provide actionable recommendations and quality metrics
Key behaviors:
- Auto-detect test framework and configuration
- Generate comprehensive coverage reports with metrics
- Activate Playwright MCP for e2e browser testing
- Provide intelligent test failure analysis
- Support continuous watch mode for development
MCP Integration
- Playwright MCP: Auto-activated for
--type e2ebrowser testing - QA Specialist Persona: Activated for test analysis and quality assessment
- Enhanced Capabilities: Cross-browser testing, visual validation, performance metrics
Tool Coordination
- Bash: Test runner execution and environment management
- Glob: Test discovery and file pattern matching
- Grep: Result parsing and failure analysis
- Write: Coverage reports and test summaries
Key Patterns
- Test Discovery: Pattern-based categorization → appropriate runner selection
- Coverage Analysis: Execution metrics → comprehensive coverage reporting
- E2E Testing: Browser automation → cross-platform validation
- Watch Mode: File monitoring → continuous test execution
Examples
Basic Test Execution
/sc:test
# Discovers and runs all tests with standard configuration
# Generates pass/fail summary and basic coverage
Targeted Coverage Analysis
/sc:test src/components --type unit --coverage
# Unit tests for specific directory with detailed coverage metrics
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.
- 3d ago First seen · 93 lines · 11 tokens per session scan A 232466ff1f5f
test is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,856 stars, last pushed 12d ago), licensed MIT. It adds 11 tokens to every session and 640 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-30.
Other commands, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
run-all-tests-and-fix
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality. All test-related commands must pass before completion.
test-run
Run all tests and report coverage to @chief.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
sdlc-test
Generate and run multi-tiered enterprise test suites (Unit, Integration, E2E, Contract, Load/k6, Chaos, and Fuzz testing).