Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/it235/multica-best-practicesnpx agentmods add skills/it235/multica-best-practices/multica-test-t3-api-automationWrote 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/it235/multica-best-practices/multica-test-t3-api-automation)<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-test-t3-api-automation"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-test-t3-api-automation/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/it235/multica-best-practices/multica-test-t3-api-automation"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-test-t3-api-automation.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.00053 | $0.00622 |
| Opus 5.5 | $0.00021 | $0.00249 |
| Sonnet 5.5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
multica-test-t3-api-automation 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.
What it actually says
API Automation (T3 · API)
T3 only after G2.5 PASS; an AC can only be verified by API → run this skill alone; if it also has a UI channel → run both, orchestration merges one report.
Integrated from
api-automation-squad. Material assembly + BLOCKED seemultica-test-orchestration.
Required Items (stop + interruption list if missing; summary from comments)
| Required | How it counts as complete |
|---|---|
| G2.5 PASS | Leader/DevOps explicit G2.5 PASS (or "G2.5 N/A" but deploy_url + Leader written authorization) |
| deploy_url | Reachable environment URL |
| contract | Apifox/OAS link, or N/A (reuse xxx) |
| Apifox three IDs | project_id / environment_id / scenario_ids complete, else N/A (not missing) |
Flow
python multica-platform-apifox/scripts/run_scenarios.py \
--project-id <id> --environment-id <id> --scenario-ids <ids> \
--deploy-url <deploy_url> --out ./reports/apifox.json
Scenario source: T2 manifest (MULTICA.md §2 API manifest) or T1 Apifox branch. Missing → interruption list.
Output and merge
# T3 API Automation — {JIRA_KEY}
- G2.5: PASS @ {sha} deploy: {url}
- Apifox: project {id} env {id} scenarios {ids}
- total / pass / fail / error
- per scenario: id / name / status / latency / assertion / log path
- conclusion: PASS | FAIL | BLOCKED
multica-test-orchestration merges with UI side: one side only verifies a given AC, missing that side → whole ticket cannot be PASS; errors → triage (references/t3-failure-triage.md).
Platform Collaboration
| Platform skill | Used for |
|---|---|
multica-platform-apifox |
Scenario run; results/logs into report |
multica-test-orchestration |
T3 gate + merge |
No local mock as a substitute for the deployed environment; no environment → BLOCKED.
Why it works
API verification is independent of UI; running after G2.5 ensures automated evidence is trustworthy; three IDs explicit avoids "silent skip".
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -57 lines · +3 tokens per session 2817b47c0514
- 1mo ago First seen · 118 lines · 50 tokens per session scan A ab0e15beda57
multica-test-t3-api-automation is a skill published in the GitHub repository it235/multica-best-practices (212 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 622 once invoked, about $0.0002 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-07.
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.