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/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/test)<a href="https://agentmods.dev/commands/random6913/claude-code-superkit/test"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/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/random6913/claude-code-superkit/test"><img src="https://agentmods.dev/badge/commands/random6913/claude-code-superkit/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.00020 | $0.01319 |
| Opus 5.5 | $0.00008 | $0.00528 |
| Sonnet 5.5 | $0.00004 | $0.00264 |
| Haiku 4.5 | $0.00002 | $0.00132 |
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 1mo 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.
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
Auto-detect the project's test runner, execute the tests for the requested scope, and report the runner's real results.
Hard Rules
- Report the runner's REAL output — paste the actual pass/fail/skip lines; never summarize from memory or invent counts.
- Consume the argument exactly as
scope+ optional--coverage; when no scope is given, default tobackend. - If the chosen scope has no matching markers (e.g.
backendon a frontend-only repo), fall back to running all detected suites — never do nothing. - Detect commands only from the Step 1–2 tables; do not invent test commands or flags.
- When a
Makefiletesttarget exists for the stack, prefermake test. - For scope
all, run every detected suite sequentially and report each separately. - On failure, show the first 5 failure details for diagnosis — no more.
Step 1 — Detect Test Runner
Scan the project root and subdirectories for stack markers:
| Marker | Test Command | Stack |
|---|---|---|
go.mod |
go test ./... -count=1 |
Go |
package.json + vitest config |
npx vitest run |
Vitest |
package.json + jest config |
npx jest |
Jest |
package.json + playwright config |
npx playwright test |
Playwright (e2e) |
cypress.config.{js,ts} |
npx cypress run |
Cypress (e2e) |
pyproject.toml / pytest.ini / conftest.py |
pytest |
Python (pytest) |
pyproject.toml with [tool.unittest] |
python -m unittest discover |
Python (unittest) |
tests/e2e/ dir + pytest |
pytest tests/e2e/ |
Python E2E (selenium) |
Cargo.toml |
cargo test |
Rust |
pom.xml |
mvn test |
Java (Maven) |
build.gradle |
./gradlew test |
Java/Kotlin (Gradle) |
Makefile with test target |
make test |
Makefile |
If a Makefile with a test target exists and the stack has one, prefer make test as it may include additional setup.
Done when: every stack present in the repo is mapped to its exact test command (or to make test).
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.
- 1mo ago First seen · 109 lines · 20 tokens per session scan A ce9b981bf91b
test is a command published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 1,319 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
ccc-audit
Audit the current project for dependency vulnerabilities, oversized bundles, type errors, dead code, hardcoded secrets, undocumented env vars and a missing CLAUDE.md. Use when you want a health score before a release or review.
validate
Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
tester
Comprehensive testing with parallel execution capabilities.
boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
verify-work
Validate built features through conversational UAT.
checklist
Generate a custom checklist for the current feature based on user requirements.