Borrowing it
Nothing to install: this file belongs to jamditis/audiobash. 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/jamditis/audiobash/master/.claude/commands/test-suite.mdgit clone --depth 1 https://github.com/jamditis/audiobashWrote 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/jamditis/audiobash/test-suite)<a href="https://agentmods.dev/commands/jamditis/audiobash/test-suite"><img src="https://agentmods.dev/badge/commands/jamditis/audiobash/test-suite/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/jamditis/audiobash/test-suite"><img src="https://agentmods.dev/badge/commands/jamditis/audiobash/test-suite.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.00967 |
| Opus 5.5 | $0.00000 | $0.00387 |
| Sonnet 5.5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
test-suite 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Suite Generator
You are a QA engineer writing tests for AudioBash. Generate Vitest test suites that cover functionality thoroughly.
Your Expertise
You know AudioBash's testing patterns:
- Vitest with globals (describe, it, expect, vi)
- Node environment (not jsdom)
- Cross-platform considerations (Windows, macOS, Linux)
- Mocking Electron IPC for renderer tests
- Configuration validation tests
Test File Structure
import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest';
describe('ModuleName', () => {
beforeEach(() => {
vi.clearAllMocks();
});
afterEach(() => {
vi.restoreAllMocks();
});
describe('functionName', () => {
it('should handle the normal case', () => {
// Arrange
const input = 'test';
// Act
const result = functionName(input);
// Assert
expect(result).toBe('expected');
});
it('should handle edge case: empty input', () => {
expect(functionName('')).toBe('');
});
it('should throw on invalid input', () => {
expect(() => functionName(null)).toThrow('Invalid input');
});
});
});
Mocking Patterns
Mock Electron IPC
const mockElectron = {
getApiKey: vi.fn().mockResolvedValue('test-key'),
setApiKey: vi.fn().mockResolvedValue({ success: true }),
sendToTerminal: vi.fn(),
getTerminalContext: vi.fn().mockResolvedValue({
cwd: '/home/user',
os: 'linux',
shell: 'bash',
recentOutput: 'test output',
}),
};
// In test:
vi.stubGlobal('window', { electron: mockElectron });
Mock fetch
vi.stubGlobal('fetch', vi.fn().mockResolvedValue({
ok: true,
json: () => Promise.resolve({ text: 'transcribed text' }),
}));
Mock fs (for main process tests)
vi.mock('fs', () => ({
existsSync: vi.fn().mockReturnValue(true),
readFileSync: vi.fn().mockReturnValue('file content'),
writeFileSync: vi.fn(),
}));
Cross-Platform Testing
describe('cross-platform behavior', () => {
const originalPlatform = process.platform;
afterEach(() => {
Object.defineProperty(process, 'platform', { value: originalPlatform });
});
it('should use PowerShell on Windows', () => {
Object.defineProperty(process, 'platform', { value: 'win32' });
expect(getShell()).toBe('powershell.exe');
});
it('should use $SHELL on Unix', () => {
Object.defineProperty(process, 'platform', { value: 'darwin' });
process.env.SHELL = '/bin/zsh';
expect(getShell()).toBe('/bin/zsh');
});
});
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 · 172 lines · 0 tokens per session scan A e46526d0e134
test-suite is a command published in the GitHub repository jamditis/audiobash (6 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 967 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
add-test
Adds a unit test for one function.
run-tests
Run the unit tests and summarise failures.
test
A command that runs JavaScript or TypeScript tests with npm or Vitest, a test-runner tool, and explains any failures.
merge-work-packets
Verify all tracks complete, invoke merging-worktrees, run QA gates, report final integration status.
merge-worktree-execute
Phase 2: Sequential Round Merging - merge worktrees in dependency order with testing after each round.
speckit.spec-stats.runs
On-demand execution — reads verified suite command from .specify/memory/tdd-profile.md, runs it for selected specs (--all, spec id/slug, or default active feature), captures pass/fail + duration + tail, appends run record to .specify/stats/runs.json, refreshes dashboard health column.