Borrowing it
Nothing to install: this file belongs to caretive-ai/project-careti. 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/caretive-ai/project-careti/main/.agents/skills/api-provider-testing/SKILL.mdgit clone --depth 1 https://github.com/caretive-ai/project-caretiWrote 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/skills/caretive-ai/project-careti/api-provider-testing)<a href="https://agentmods.dev/skills/caretive-ai/project-careti/api-provider-testing"><img src="https://agentmods.dev/badge/skills/caretive-ai/project-careti/api-provider-testing/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/skills/caretive-ai/project-careti/api-provider-testing"><img src="https://agentmods.dev/badge/skills/caretive-ai/project-careti/api-provider-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 55 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 58 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Agent Snooping · line 115 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00905 |
| Opus 5 | $0.00000 | $0.00452 |
| Sonnet 5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
api-provider-testing 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Provider Testing Skill
Overview
Guidelines for testing LLM API providers when adding or modifying support in Caret.
Test Categories
1. Basic Conversation Test
- Simple prompt → response verification
- Streaming chunk reception
- Token usage reporting
Example:
const response = await handler.createMessage("System prompt", [
{ role: 'user', content: 'Hello' }
])
// Verify: text chunks + usage chunk
2. Tool Calling Test
Core verification for agentic capabilities.
Test Flow:
- Send message with tool definitions
- Verify
tool_callschunk received - Verify function name and arguments
- Send tool result back
- Verify final text response
Provider-Specific Formats:
| Provider | Tool Call Key | Arguments | Tool Result Key |
|---|---|---|---|
| OpenAI | tool_calls |
string | tool_call_id |
| Naver Cloud | toolCalls |
object | toolCallId |
| Upstage | tool_calls |
string | tool_call_id |
| Gemini | functionCall |
object | n/a (different format) |
3. Timeout Test
- Use
AbortControllerwith configurable timeout - Default: 60 seconds recommended
- Verify timeout error is thrown correctly
4. Error Handling Test
- Invalid API key → 401/403 error
- Rate limiting → 429 error with retry
- Empty response → specific error message
Test Script Template
Location: scripts/test-{provider}-api.js
// Load .env
const fs = require('fs')
const path = require('path')
const envPath = path.resolve(__dirname, '../.env')
if (fs.existsSync(envPath)) {
fs.readFileSync(envPath, 'utf-8').split('\n').forEach((line) => {
const match = line.match(/^([^=]+)=(.*)$/)
if (match && !process.env[match[1]]) {
process.env[match[1]] = match[2]
}
})
}
// Test structure
async function testBasicConversation() { ... }
async function testToolCalling() { ... }
async function testToolResultFlow() { ... }
async function testTimeout() { ... }
async function main() {
const results = {
basic: await testBasicConversation(),
toolCall: await testToolCalling(),
toolFlow: await testToolResultFlow(),
}
console.log('Results:', results)
}
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.
- 9d ago First seen · 118 lines · 0 tokens per session scan A e481b133aca1
api-provider-testing is a skill published in the GitHub repository caretive-ai/project-careti (47 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 905 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 skills, from other repositories
coco-delivery
Implement and verify CoCo features end-to-end (Telegram commands, callbacks, app-server transport, queueing, watchdogs, approvals, and tests). Use when changing this repository's bot behavior and needing repo-specific file targets, workflows, and validation commands. NOT for generic Python tasks outside CoCo.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
convex-test
Generate convex-test tests for the app's Convex functions.