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.
git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-test)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-test"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-test/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.
<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-test"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-test.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00654 |
| Opus 5.5 | $0.00004 | $0.00262 |
| Sonnet 5.5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00065 |
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 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.
This is a copy
95% identical to test — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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:sc: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: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:sc:test
# Discovers and runs all tests with standard configuration
# Generates pass/fail summary and basic coverage
Targeted Coverage Analysis
/sc: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.
- 2mo ago First seen · 93 lines · 11 tokens per session scan A a3659fff35e4
test is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 654 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to test, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
test
Execute tests with coverage analysis and automated quality reporting.
9_gofer_tests
Generate comprehensive test suites from four testing perspectives for a target component.
test
Execute tests with coverage analysis and automated quality reporting.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.