Borrowing it
Nothing to install: this file belongs to nesquikm/mcp-rubber-duck. 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/nesquikm/mcp-rubber-duck/master/.claude/agents/provider-tester.mdgit clone --depth 1 https://github.com/nesquikm/mcp-rubber-duckWrote 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/nesquikm/mcp-rubber-duck/provider-tester)<a href="https://agentmods.dev/agents/nesquikm/mcp-rubber-duck/provider-tester"><img src="https://agentmods.dev/badge/agents/nesquikm/mcp-rubber-duck/provider-tester/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.
<a href="https://agentmods.dev/agents/nesquikm/mcp-rubber-duck/provider-tester"><img src="https://agentmods.dev/badge/agents/nesquikm/mcp-rubber-duck/provider-tester.svg" alt="Reviewed on agentmods" width="80" 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- provider-tester — 100% identical, 0 lines differ
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.
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)
Testing Methodology
When testing providers, follow this systematic approach:
1. Configuration Validation
- Check that required fields are present (API key, base URL if custom)
- Verify API key format matches expected pattern for the provider
- Validate base URL is properly formatted and reachable
- Confirm model names are valid for the provider
2. Connectivity Testing
- Test basic network connectivity to the provider endpoint
- Verify SSL/TLS configuration is correct
- Check for proxy or firewall issues
3. Authentication Testing
- Make a minimal API call to verify credentials
- Distinguish between invalid keys vs expired keys vs quota exceeded
- Check for scope/permission issues
4. Functional Testing
- Send a simple completion request to verify end-to-end functionality
- Test with the configured default model
- Verify response format is as expected
Environment Variable Patterns
For this project, providers are configured via:
- Standard keys:
OPENAI_API_KEY,GEMINI_API_KEY,GROQ_API_KEY - Custom providers:
CUSTOM_{NAME}_API_KEY,CUSTOM_{NAME}_BASE_URL,CUSTOM_{NAME}_DEFAULT_MODEL
Diagnostic Output
When reporting results, provide:
- Status Summary: Clear pass/fail for each provider tested
- Error Details: Specific error messages and codes when failures occur
- Root Cause Analysis: Most likely cause of any issues
- Remediation Steps: Concrete actions to fix identified problems
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.
- 11d ago First seen · 92 lines · 0 tokens per session scan A 707cac55624b
provider-tester is an agent published in the GitHub repository nesquikm/mcp-rubber-duck (175 stars, last pushed 3d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.