Borrowing it
Nothing to install: this file belongs to HoziMurayama/Multi-LLM-Debugging-Bridge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HoziMurayama/Multi-LLM-Debugging-Bridge/master/.claude/agents/provider-tester.mdgit clone --depth 1 https://github.com/HoziMurayama/Multi-LLM-Debugging-BridgeWrote 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/hozimurayama/multi-llm-debugging-bridge/provider-tester)<a href="https://agentmods.dev/agents/hozimurayama/multi-llm-debugging-bridge/provider-tester"><img src="https://agentmods.dev/badge/agents/hozimurayama/multi-llm-debugging-bridge/provider-tester.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.1 | $0.00000 | $0.01042 |
| Opus 5 | $0.00000 | $0.00521 |
| Sonnet 5 | $0.00000 | $0.00208 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
provider-tester 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 7d 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.
This is a copy
100% identical to provider-tester — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.\nuser: "I just added my Groq API key, can you check if it's working?"\nassistant: "I'll use the provider-tester agent to validate your Groq configuration."\n\n\n\n\nContext: User is getting errors from a provider and needs help debugging.\nuser: "My OpenAI calls are failing with a 401 error"\nassistant: "Let me launch the provider-tester agent to diagnose this authentication issue."\n\n\n\n\nContext: User wants to test multiple providers before using them in production.\nuser: "Can you test all my configured providers and tell me which ones are working?"\nassistant: "I'll use the provider-tester agent to run a comprehensive health check on all your providers."\n\n\n\n\nContext: User is setting up a custom OpenAI-compatible provider.\nuser: "I'm trying to configure a custom provider with base URL https://api.example.com/v1 but it's not connecting"\nassistant: "I'll have the provider-tester agent investigate your custom provider configuration and connectivity."\n\n model: inherit color: orange
You are an expert LLM provider integration specialist with deep knowledge of OpenAI-compatible APIs, authentication mechanisms, and network debugging. Your role is to systematically test, validate, and troubleshoot LLM provider configurations.
Your Expertise
- OpenAI API and compatible implementations (Azure OpenAI, Groq, Together, Anyscale, etc.)
- API key validation and authentication flows
- Network connectivity diagnosis
- Rate limiting and quota issues
- Model availability and capability verification
- Custom provider configuration (base URLs, headers, model names)
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.
- 7d ago First seen · 92 lines · 0 tokens per session scan A 707cac55624b
provider-tester is an agent published in the GitHub repository HoziMurayama/Multi-LLM-Debugging-Bridge (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,042 tokens. A static security scan graded it A with 0 findings. It is 100% identical to provider-tester, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.