Borrowing it
Nothing to install: this file belongs to Kynto-Consulting/capsule. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kynto-Consulting/capsule/main/.claude/commands/test.mdgit clone --depth 1 https://github.com/Kynto-Consulting/capsuleWrote 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/kynto-consulting/capsule/test)<a href="https://agentmods.dev/commands/kynto-consulting/capsule/test"><img src="https://agentmods.dev/badge/commands/kynto-consulting/capsule/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/kynto-consulting/capsule/test"><img src="https://agentmods.dev/badge/commands/kynto-consulting/capsule/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.00000 | $0.00805 |
| Opus 5.5 | $0.00000 | $0.00322 |
| Sonnet 5.5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00081 |
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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Commands — Capsule
Overview
Instructions for running the full test suite across all Capsule packages.
Run All Tests
make test
Backend Tests (Go)
# Run all backend tests
cd backend
go test ./...
# Run with verbose output
go test -v ./...
# Run with race detector
go test -race ./...
# Run a specific package
go test -v ./internal/server/...
# Run a specific test function
go test -v -run TestCreateEnvironment ./internal/server/...
# Run with coverage
go test -coverprofile=coverage.out ./...
go tool cover -html=coverage.out -o coverage.html
# Run integration tests (requires running database)
go test -tags=integration -v ./...
# Short mode (skip long-running tests)
go test -short ./...
Backend Test Conventions
- Unit tests live alongside source files:
handler.go→handler_test.go - Integration tests use build tag
//go:build integration - Table-driven tests are preferred
- Use
testify/assertandtestify/requirefor assertions - Mock interfaces with
gomockor hand-written mocks ininternal/mocks/
Frontend Tests (Next.js)
# Run all frontend tests
cd frontend
pnpm test
# Run in watch mode
pnpm test:watch
# Run with coverage
pnpm test:coverage
# Run a specific test file
pnpm test -- --testPathPattern="components/Dashboard"
# Run E2E tests (Playwright)
pnpm test:e2e
# Run E2E in headed mode (visible browser)
pnpm test:e2e -- --headed
Frontend Test Conventions
- Unit tests:
ComponentName.test.tsxalongside component - Use React Testing Library for component tests
- Use MSW (Mock Service Worker) for API mocking
- E2E tests live in
frontend/e2e/
CLI Tests (Go)
# Run all CLI tests
cd cli
go test ./...
# Run with verbose output
go test -v ./...
# Run with race detector
go test -race ./...
# Run a specific command test
go test -v -run TestDeployCommand ./cmd/...
# Run with coverage
go test -coverprofile=coverage.out ./...
go tool cover -func=coverage.out
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 · 165 lines · 0 tokens per session scan A be58c7fdc5ec
test is a command published in the GitHub repository Kynto-Consulting/capsule (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 805 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.
Other commands, from other repositories
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.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.