test

A command for generating and running software tests, including coverage checks and watch mode. It follows the test framework and patterns already used in the project.

In plain words
What is it for?
Use it to create tests for a file or feature, run the existing test suite, view a test-coverage report, or rerun tests as code changes.
Why use it?
It reduces the manual work of deciding which cases to test and running tests repeatedly. It also helps check normal behavior, errors, edge cases, and integrations.

Command

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/felipeslo/opencode-kit/test
Clone the repo
git clone --depth 1 https://github.com/felipeslo/opencode-kit
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 625 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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00625
Opus 5 $0.00007 $0.00313
Sonnet 5 $0.00003 $0.00125
Haiku 4.5 $0.00001 $0.00063

Measured yesterday against content hash 420414646890, 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.

.opencode/commands/test.md · 145 lines

How it starts

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

/test - Test Generation and Execution

$ARGUMENTS


Purpose

This command generates tests, runs existing tests, or checks test coverage.


Sub-commands

/test                - Run all tests
/test [file/feature] - Generate tests for specific target
/test coverage       - Show test coverage report
/test watch          - Run tests in watch mode

Behavior

Generate Tests

When asked to test a file or feature:

  1. Analyze the code

    • Identify functions and methods
    • Find edge cases
    • Detect dependencies to mock
  2. Generate test cases

    • Happy path tests
    • Error cases
    • Edge cases
    • Integration tests (if needed)
  3. Write tests

    • Use project's test framework (Jest, Vitest, etc.)
    • Follow existing test patterns
    • Mock external dependencies

Output Format

For Test Generation

## 🧪 Tests: [Target]

### Test Plan
| Test Case | Type | Coverage |
|-----------|------|----------|
| Should create user | Unit | Happy path |
| Should reject invalid email | Unit | Validation |
| Should handle db error | Unit | Error case |

### Generated Tests

`tests/[file].test.ts`

[Code block with tests]

---

Run with: `npm test`

For Test Execution

🧪 Running tests...

✅ auth.test.ts (5 passed)
✅ user.test.ts (8 passed)
❌ order.test.ts (2 passed, 1 failed)

Failed:
  ✗ should calculate total with discount
    Expected: 90
    Received: 100

Total: 15 tests (14 passed, 1 failed)

Examples

/test src/services/auth.service.ts
/test user registration flow
/test coverage
/test fix failed tests

Test Patterns

Unit Test Structure

describe('AuthService', () => {
  describe('login', () => {
    it('should return token for valid credentials', async () => {
      // Arrange
      const credentials = { email: '[email protected]', password: 'pass123' };
      
      // Act
      const result = await authService.login(credentials);
      
      // Assert
      expect(result.token).toBeDefined();
    });

    it('should throw for invalid password', async () => {
      // Arrange
      const credentials = { email: '[email protected]', password: 'wrong' };
      
      // Act & Assert
      await expect(authService.login(credentials)).rejects.toThrow('Invalid credentials');
    });
  });
});

Read the full file on GitHub · 145 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.

  1. yesterday First seen · 145 lines · 14 tokens per session scan A 420414646890

Subscribe to this mod's changes

test is a command published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 625 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.