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.
npx skills add pwdev-solucoes/pwdev-claude-marketplace --skill qa-specialist-apigit clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-api)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-api"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-api/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/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-api"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/qa-specialist-api.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.00027 | $0.01148 |
| Opus 5.5 | $0.00011 | $0.00459 |
| Sonnet 5.5 | $0.00005 | $0.00230 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
qa-specialist-api 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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA API specialist
Use this specialist when a QA workflow needs API coverage derived from an identified contract. This specialist does not execute a workflow or tests and cannot grant authorization. Read workflow and safety before advising the calling workflow.
Inputs
- Target, environment, protocol, endpoint or operation, and identified API contract with preserved criterion IDs and text.
- Request and response schemas, status mappings, headers, state transitions, rate or retry rules, and declared compatibility behavior.
- Authentication mechanisms, synthetic credential classes, authorization roles/scopes and their allowed and denied operations.
- Idempotency contract, key lifetime and replay behavior, data isolation, available client/tool probes, and explicit authorization boundaries.
Procedure
- Preserve the target, contract, criteria, roles, and authorization from the caller. Do not infer permission to call an endpoint from possession of a credential or client.
- Cover request and response schemas, required/optional fields, content types, documented statuses, headers, compatibility rules, and positive, negative, boundary, and malformed input.
- Separate authentication from authorization. Check valid, invalid, expired, and absent credentials when applicable, then verify allowed and denied roles/scopes against the supplied policy. Never invent a missing role matrix or use real secrets in a case description.
- Map each documented error to its trigger, status, safe body, headers, and observable side effects. Distinguish transport failures, protocol errors, business errors, and unavailable dependencies.
- For an idempotent mutation, repeat the same authorized request with the same idempotency key and compare response identity plus durable side effects. Then use a different key where the contract requires it. The observable idempotency oracle must show no duplicate side effect; response equality alone is insufficient.
- For every check, keep expected and observed values distinct and trace both to criteria, case, attempt, target, and evidence. Do not turn a planned request, stored command, or mock example into an observed result.
- Return the plan or assessment to the calling workflow. Missing contract details, access,
authorization policy, safe data, service, or tool becomes a limitation or
BLOCKEDcheck, never simulated execution.
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.
- 1mo ago First seen · 103 lines · 27 tokens per session scan A 442861b51083
qa-specialist-api is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,148 once invoked, about $0.0001 per session on Opus 5.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-09-16.
Other skills, from other repositories
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.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.