Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/claude-market/marketplacenpx agentmods add commands/claude-market/marketplace/testWrote 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/claude-market/marketplace/test)<a href="https://agentmods.dev/commands/claude-market/marketplace/test"><img src="https://agentmods.dev/badge/commands/claude-market/marketplace/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/claude-market/marketplace/test"><img src="https://agentmods.dev/badge/commands/claude-market/marketplace/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.03474 |
| Opus 5 | $0.00005 | $0.01737 |
| Sonnet 5 | $0.00002 | $0.00695 |
| Haiku 4.5 | $0.00001 | $0.00347 |
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 8d 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 — 605 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecForge Test Orchestrator
Run comprehensive tests with behavior observation, diagnose failures, and iterate until all tests pass.
Overview
The test orchestrator runs tests at multiple levels and uses behavior observation to diagnose and fix issues:
- Unit Tests - Test individual handlers and functions
- Integration Tests - Test API endpoints end-to-end
- Contract Tests - Verify API matches OpenAPI spec
- Behavior Observation - Monitor test execution to identify issues
- Iterative Fixing - Diagnose and fix failures automatically
Test Orchestration Flow
┌─────────────────────────────────────────────┐
│ /specforge:test │
└─────────────────┬───────────────────────────┘
│
┌─────────────┼─────────────┬──────────────┐
▼ ▼ ▼ ▼
┌────────┐ ┌──────────┐ ┌──────────┐ ┌─────────────┐
│ Unit │ │ Integration│ │ Contract │ │ E2E Tests │
│ Tests │ │ Tests │ │ Tests │ │ (optional) │
└────┬───┘ └─────┬────┘ └─────┬────┘ └──────┬──────┘
│ │ │ │
└────────────┴─────────────┴──────────────┘
│
▼
┌──────────────────────┐
│ Behavior Observation │
│ & Failure Diagnosis │
└──────────────────────┘
│
▼
┌──────────────────────┐
│ Iterate & Fix │
│ (Max 3 iterations) │
└──────────────────────┘
Step 1: Read Configuration
Extract the tech stack configuration from CLAUDE.md:
# Read SpecForge configuration
grep "SpecForge configuration" -A 10 CLAUDE.md
Extract:
- Backend plugin
- Database plugin
- Codegen plugin
- Frontend plugin (if applicable)
Step 2: Unit Tests
Run unit tests for the backend using the backend plugin's testing expert:
# Get backend plugin
BACKEND_PLUGIN=$(grep "backend:" CLAUDE.md | cut -d: -f2 | tr -d ' ')
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.
- 8d ago First seen · 605 lines · 11 tokens per session scan A 85219964a6f9
test is a command published in the GitHub repository claude-market/marketplace (22 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 3,474 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
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
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…