nesquikm

Provider Tester — Testing & QA agent for Claude Code

Testing & QA community

Use this agent when you need to test, debug, or validate LLM provider configurations.

How to install Provider Tester

Installs to ~/.claude/agents/nesquikm-mcp-rubber-duck-provider-tester.md

Terminal
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/nesquikm/mcp-rubber-duck/HEAD/.claude/agents/provider-tester.md -o ~/.claude/agents/nesquikm-mcp-rubber-duck-provider-tester.md

Restart Claude Code, or start a new session, for it to be picked up.

What Provider Tester does


name: provider-tester description: Use this agent when you need to test, debug, or validate LLM provider configurations. This includes verifying API keys work correctly, checking provider connectivity, testing model availability, debugging authentication issues, validating base URLs for custom providers, or troubleshooting why a specific provider isn't responding as expected.\n\nExamples:\n\n\nContext: User has just added a new provider configuration and wants to verify it works.\nu

Alternatives in Testing & QA

  • Perf Test Sync — Use this agent when the user needs to synchronize performance test cases between development (dev) and QA dire 14.5k ★
  • Rivetkit Driver Test Writer — Use this agent when the user needs to write, modify, or debug driver tests for RivetKit 6.1k ★
  • QA Debug Analyst 597 ★

Full documentation available on GitHub

View Source Repository