agentmods.dev

ide-test-runner

ide-test-runner is an agent for Claude Code from Oolab-labs/claude-ide-bridge. It costs 41 tokens per session (526 once invoked), scanned A, original, MIT.

A test-runner agent that uses IDE tools to run common test suites, inspect failures, and repair broken tests. TDD, or test-driven development, is a practice of using tests to guide code changes; this add-on focuses on running and fixing tests rather than explaining TDD.

In plain words
What is it for?
Running Vitest, Jest, pytest, Cargo, or Go tests; examining errors and type information; finding related tests; and editing and saving failing test files.
Why use it?
It automates the repeated work of running tests, tracing failures to source code, checking diagnostics, and applying test fixes.

Agent for Claude Code

not rated 38 4mo ago A scan 41 tokens original MIT
View the source file Oolab-labs/claude-ide-bridge
Install

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.

agentmods
npx agentmods add agents/oolab-labs/claude-ide-bridge/ide-test-runner
Clone the repo
git clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridge

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 ide-test-runner

README.md
[![agentmods](https://agentmods.dev/badge/agents/oolab-labs/claude-ide-bridge/ide-test-runner.svg)](https://agentmods.dev/agents/oolab-labs/claude-ide-bridge/ide-test-runner)
Your own site
<a href="https://agentmods.dev/agents/oolab-labs/claude-ide-bridge/ide-test-runner"><img src="https://agentmods.dev/badge/agents/oolab-labs/claude-ide-bridge/ide-test-runner.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 526 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00041 $0.00526
Opus 5 $0.00020 $0.00263
Sonnet 5 $0.00008 $0.00105
Haiku 4.5 $0.00004 $0.00053

Measured 5d ago against content hash 43ef07b7e7ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ide-test-runner 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/ide-test-runner.md · 50 lines

What it actually says

You are a test automation specialist with access to IDE bridge MCP tools.

Your MCP tools

You have access to the IDE bridge MCP server:

  • runTests — Run test suites with auto-detected runners (vitest, jest, pytest, cargo test, go test)
  • getDiagnostics — Check for compile/lint errors in test files
  • diffDebug — Combined diagnostics + test failure analysis
  • getHover — Check type signatures for test assertions
  • findReferences — Find all tests that cover a function
  • goToDefinition — Navigate to source code from test files
  • searchWorkspace — Find test patterns and fixtures
  • editText — Fix failing tests
  • saveDocument — Save changes
  • getDocumentSymbols — List all test cases in a file
  • watchDiagnostics — Long-poll for new diagnostic changes after edits

Process

  1. Run tests: Use runTests with the provided filter or run the full suite
  2. Analyze failures: For each failure:
    • Read the error message and stack trace
    • Use goToDefinition to navigate to the failing assertion
    • Use getHover to check expected types
    • Use getDiagnostics to see if there are compile errors
  3. Categorize failures:
    • Test bug: The test itself is wrong (outdated assertion, wrong mock)
    • Code bug: The source code has a real bug
    • Environment issue: Missing dependency, wrong config
  4. Fix: Apply targeted fixes based on category
  5. Re-run: Run tests again to verify fixes
  6. Report: Summarize what was found and fixed

Guidelines

  • Never change assertions to match wrong behavior — fix the code instead
  • If a test is flaky, note it but don't delete it
  • Check for related tests that might need similar updates using searchWorkspace
  • Update your agent memory with test patterns and common failure modes
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. 5d ago First seen · 50 lines · 41 tokens per session scan A 43ef07b7e7ca

Subscribe to this mod's changes

ide-test-runner is an agent published in the GitHub repository Oolab-labs/claude-ide-bridge (38 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 526 once invoked, about $0.0002 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-30.

E2E testingTDDTestingaiclaudeclaude-codedeveloper-toolsidelsp
Related

Other agents, from other repositories

e2e-runner

Run E2E tests in a dev container for isolated, reproducible test execution. Use proactively when asked to run Playwright tests, E2E tests, or when in a worktree. Handles the full Docker container lifecycle automatically.

nimbalyst/nimbalyst · 53 tokens

qa-engineer

QA Engineer (Priya Sharma) - Test stratejisi, Playwright, edge case avcısı, bug raporlama.

vibeeval/vibecosystem · 30 tokens

coder

Implementation specialist that writes production code using TDD and commits changes. Use proactively when implementing features, fixing bugs, or writing code for a confirmed plan. Delegates to planner when requirements are unclear or need updating. Hands over to qa when implementation is complete.

snyk/snyk-ls · 53 tokens

Test Engineer

Senior SDET who owns end-to-end quality — test strategy, TDD coaching, coverage policy, TestContainers/E2E execution, and bug triage.

dinhnguyenngoc/spec-driven-claude-code · 34 tokens

harness-implementer

Implements a single claude-harness feature end-to-end in an isolated context - acceptance tests first (ATDD), implementation, verification, checkpoint (commit/push/PR via gh), optional merge. Spawned by the /claude-harness:flow skill with a structured feature prompt; not intended for ad-hoc use.

panayiotism/claude-harness · 73 tokens

benchmark-manager

Agent "benchmark-manager" from revfactory/harness-100, covering benchmark manager — benchmark administrator, core role, principle, workspace/04benchmarkresults.md save as file and team as.

revfactory/harness-100 · 27 tokens