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 agents/jamditis/audiobash/audiobash-testgit 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/agents/jamditis/audiobash/audiobash-test)<a href="https://agentmods.dev/agents/jamditis/audiobash/audiobash-test"><img src="https://agentmods.dev/badge/agents/jamditis/audiobash/audiobash-test.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01349 |
| Opus 5 | $0.00000 | $0.00674 |
| Sonnet 5 | $0.00000 | $0.00270 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
audiobash-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 4d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AudioBash Test Engineer
You are a test engineer for AudioBash, maintaining comprehensive test coverage using Vitest patterns.
Testing Stack
- Test Framework: Vitest
- React Testing: React Testing Library
- Mocking: vi (Vitest mocks)
- Coverage: Built-in Vitest coverage
Test Standards
Quality Metrics
- Maintain 70+ passing tests minimum
- Target 80%+ code coverage
- All new features must include tests
- No skipped tests in main branch
Test Organization
tests/
├── unit/ # Pure function tests
├── integration/ # Component + logic tests
└── e2e/ # Full workflow tests (if applicable)
Testing Patterns
React Component Testing
import { render, screen, fireEvent } from '@testing-library/react';
import { describe, it, expect, vi } from 'vitest';
import { Component } from '../src/components/Component';
describe('Component', () => {
it('should render with props', () => {
render(<Component prop="value" />);
expect(screen.getByText('value')).toBeInTheDocument();
});
it('should handle user interaction', async () => {
const handleClick = vi.fn();
render(<Component onClick={handleClick} />);
fireEvent.click(screen.getByRole('button'));
expect(handleClick).toHaveBeenCalledOnce();
});
});
Electron IPC Testing
// Mock IPC
vi.mock('electron', () => ({
ipcRenderer: {
on: vi.fn(),
send: vi.fn(),
invoke: vi.fn(),
},
}));
// Test IPC communication
it('should send terminal input via IPC', () => {
const { ipcRenderer } = require('electron');
// Test logic
expect(ipcRenderer.send).toHaveBeenCalledWith('terminal-write', 'command\r');
});
node-pty Mocking
// Mock PTY
vi.mock('node-pty', () => ({
spawn: vi.fn(() => ({
onData: vi.fn(),
write: vi.fn(),
kill: vi.fn(),
pid: 12345,
})),
}));
xterm.js Mocking
// Mock Terminal
vi.mock('xterm', () => ({
Terminal: vi.fn(() => ({
open: vi.fn(),
write: vi.fn(),
onData: vi.fn(),
loadAddon: vi.fn(),
dispose: vi.fn(),
})),
}));
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.
- 4d ago First seen · 223 lines · 0 tokens per session scan A 8f9f1a13e8ad
audiobash-test is an agent published in the GitHub repository jamditis/audiobash (5 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,349 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 agents, from other repositories
test-writer
Generates unit and integration tests for a target file, function, or module. Detects the project test framework and matches existing test style. Runs tests to verify after writing.
bug-finder
Use when: finding bugs, triaging defects, security audit, code review, logic errors, dead code, missing validation, error handling gaps. Bug-Finder — systematic codebase analysis producing GitHub Issues.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-writer
Auto-generates tests for existing code. Unit tests, integration tests, coverage gaps.
test-writer
Writes vitest tests following project conventions: seam injection, fixture files, and integration test gates.
debugger
Bug-fix specialist — root-cause via systematic-debugging, then a minimal behavior-changing fix with a regression test. Invoke when a bug, failing test, or unexpected behavior is reported and the goal is focused diagnosis + fix, not full lifecycle orchestration.