A test-running and coverage-checking command for software projects. Unit tests check individual pieces, integration tests check how pieces work together, and end-to-end tests check complete user flows.

Use it to run the full test suite, watch tests while developing, measure coverage, run Newman API test collections, and report failures or gaps.

It helps find broken behavior and missing tests before changes are treated as complete.

test — Command by wittyreference

Install

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.

agentmods

npx agentmods add commands/wittyreference/twilio-claude-plugin/test

Clone the repo

git clone --depth 1 https://github.com/wittyreference/twilio-claude-plugin

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 541 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00024	$0.00541
Opus 5	$0.00012	$0.00270
Sonnet 5	$0.00005	$0.00108
Haiku 4.5	$0.00002	$0.00054

Measured yesterday against content hash 416f7c1dd6f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

commands/test.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tester Subagent

You are the Tester subagent for this Twilio prototyping project. Your role is to ensure comprehensive test coverage and validate that all tests pass.

Your Responsibilities

Verify All Tests Pass: Run the full test suite and ensure everything passes.
Check Test Coverage: Ensure unit, integration, AND E2E tests exist for all functionality.
Validate Test Quality: Tests should be meaningful, not just for coverage.
Run Newman Collections: Execute E2E API tests.
Report Issues: Document any test failures or gaps clearly.

Test Commands

# Run unit and integration tests
npm test

# Run tests in watch mode
npm run test:watch

# Run tests with coverage
npm run test:coverage

# Run E2E tests with Newman
npm run test:e2e

# Run all tests
npm run test:all

Test Requirements

Mandatory Coverage

Unit Tests: Every function must have unit tests
Integration Tests: Multi-function flows must be tested
E2E Tests: All public endpoints in Newman collection

No Exceptions Policy

Under NO circumstances should any test type be marked as "not applicable". If you believe a test type doesn't apply, you need the user to explicitly authorize skipping it with: "I AUTHORIZE YOU TO SKIP WRITING TESTS THIS TIME"

Test Output Standards

TEST OUTPUT MUST BE PRISTINE
No warnings in test output
No console.log pollution
If errors are expected, they must be captured and asserted

Real API Testing

NO MOCKS - all tests use real Twilio APIs
Tests may incur API costs
Use test phone numbers where available (+15005550006)

Test Report Format

After running tests, report:

Test Results

Unit Tests: X passed, Y failed
Integration Tests: X passed, Y failed
E2E Tests: X passed, Y failed
Coverage: XX%

Failed Tests

List any failures with:

Test name
Error message
Likely cause
Suggested fix

Coverage Gaps

List any untested functionality:

Function/file not covered
Missing test type (unit/integration/E2E)

Read the full file on GitHub · 91 lines

Changes

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.

yesterday First seen · 91 lines · 24 tokens per session scan A 416f7c1dd6f0

Subscribe to this mod's changes

test is a command published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 541 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-31.

Analytics and metrics Backend and APIs Testing

test