audiobash: Agent for Claude Code

.claude/agents/audiobash-test.md

audiobash-test is an agent for Claude Code from jamditis/audiobash. It costs 0 tokens per session (1,349 once invoked), scanned A, original, MIT.

A test-engineering agent for AudioBash that creates automated tests with Vitest and React Testing Library. Automated tests check that code behaves as expected without requiring every case to be tested manually.

In plain words
What is it for?
Use it to write tests for functions and React components, simulate user interactions, mock Electron communication, validate configuration, and consider Windows, macOS, and Linux differences.
Why use it?
It helps catch broken behavior, missing edge cases, and regressions while keeping tests organized across units, integrations, and end-to-end workflows.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is jamditis/audiobash's own configuration. It tells Claude Code how to work on audiobash itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything audiobash configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { Component } from '../src/components/Component';.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jamditis/audiobash/master/.claude/agents/audiobash-test.md
Clone the repo
git clone --depth 1 https://github.com/jamditis/audiobash

Made for: Claude Code.

Wrote 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.

agentmods badge for audiobash-test

README.md
[![agentmods](https://agentmods.dev/badge/agents/jamditis/audiobash/audiobash-test/github.svg)](https://agentmods.dev/agents/jamditis/audiobash/audiobash-test)
Your own site
<a href="https://agentmods.dev/agents/jamditis/audiobash/audiobash-test"><img src="https://agentmods.dev/badge/agents/jamditis/audiobash/audiobash-test/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.

agentmods 80×15 button for audiobash-test

Your own site · 80×15
<a href="https://agentmods.dev/agents/jamditis/audiobash/audiobash-test"><img src="https://agentmods.dev/badge/agents/jamditis/audiobash/audiobash-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,349 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01349
Opus 5.5 $0.00000 $0.00540
Sonnet 5.5 $0.00000 $0.00270
Haiku 4.5 $0.00000 $0.00135

Measured 2mo ago against content hash 8f9f1a13e8ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/agents/audiobash-test.md · 223 lines

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(),
  })),
}));

Read the full file on GitHub · 223 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. 2mo ago First seen · 223 lines · 0 tokens per session scan A 8f9f1a13e8ad

Subscribe to this mod's changes

audiobash-test is an agent 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 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.

Related

Other agents, from other repositories

test-automator

Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.

echoVic/blade-code · 46 tokens

tester

A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.

Insajin/autopus-adk · 38 tokens

pr-test-analyzer

Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough…

fuxicodex/Fuxi · 101 tokens

tester

Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…

opencue/cuecards · 349 tokens

test-runner

Test writing and execution agent. Use for writing tests, running test suites, maintaining test coverage, and ensuring code quality through testing.

randomittin/heimdall · 30 tokens

test-runner

Unit and integration test execution with intelligent failure triage and debugging.

FortiumPartners/ensemble · 16 tokens