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.
npx agentmods add commands/felipeslo/opencode-kit/testgit clone --depth 1 https://github.com/felipeslo/opencode-kitWhat 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.00014 | $0.00625 |
| Opus 5 | $0.00007 | $0.00313 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00063 |
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.
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:
-
Analyze the code
- Identify functions and methods
- Find edge cases
- Detect dependencies to mock
-
Generate test cases
- Happy path tests
- Error cases
- Edge cases
- Integration tests (if needed)
-
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');
});
});
});
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 · 145 lines · 14 tokens per session scan A 420414646890
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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.