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/jamditis/audiobash/test-suitegit clone --depth 1 https://github.com/jamditis/audiobashWhat 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.00000 | $0.00967 |
| Opus 5 | $0.00000 | $0.00483 |
| Sonnet 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 3d 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.
- 3d ago First seen · 172 lines · 0 tokens per session scan A e46526d0e134
test-suite is a command published in the GitHub repository jamditis/audiobash (5 stars, last pushed 4d 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
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
go-test
Go TDD workflow with table-driven tests.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test-ts
Run TypeScript tests for Solana frontends and Anchor programs.
run-all-tests-and-fix
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality. All test-related commands must pass before completion.
generate-tests
Generate unit or integration tests for Go code following project patterns and coverage targets.