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 it235/multica-best-practices --skill multica-platform-apifoxgit clone --depth 1 https://github.com/it235/multica-best-practicesWrote 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-platform-apifox)<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-platform-apifox"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-platform-apifox/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-platform-apifox"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-platform-apifox.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.00035 | $0.00295 |
| Opus 5.5 | $0.00014 | $0.00118 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
multica-platform-apifox 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
Apifox Platform
Responsibility
Integrate Apifox: read API contracts/scenarios, run test scenarios, and (during T1) supplement scenarios by contract. All Apifox credentials and the apifox-cli tool are only looked up here.
Capabilities
fetch_contract.py: pull API contract (OAS/Apifox) by project/environment.run_scenarios.py: run scenario IDs against a deployed environment, return logs/assertions.
Usage (Tester)
- T1: supplement scenarios by contract (AI branch) → record in Confluence + manifest (MULTICA.md §2).
- T3:
run_scenarios.py --project-id <id> --environment-id <id> --scenario-ids <ids> --deploy-url <url>→ join overall verdict.
Credentials
APIFOX_TOKEN/ project credentials via environment variables or Secret; seescripts/run_scenarios.py --help.- Never hardcode tokens in skill content.
What ships with it
27 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.
- .apifox/.gitignore 95 B
- .apifox/systems-registry.example.json 252 B
- .env.example 204 B
- config.yaml 721 B
- references/agent-instructions.md 3.1 KB
- references/CHANGELOG.md 723 B
- references/openapi-branch-workflow.md 3.1 KB
- references/reference.md 13 KB
- references/supplement-workflow.md 13 KB
- scripts/append-to-scenario.js 6.9 KB runs code
- scripts/batch-create.ps1 5.0 KB runs code
- scripts/config.example.json 3.3 KB
- scripts/discover-auth.js 13 KB runs code
- scripts/discover-scenario-target.js 5.0 KB runs code
- scripts/generate-cases.js 16 KB runs code
- scripts/lib/apifox.js 4.6 KB runs code
- scripts/requirements.txt 12 B
- scripts/run_apifox.py 3.8 KB runs code
- scripts/safe-update-case.js 4.1 KB runs code
- scripts/sync_openapi.js 5.2 KB runs code
- scripts/systems-registry.js 6.9 KB runs code
- scripts/validate-config.js 551 B runs code
- tests/apifox-lib.test.js 1.9 KB runs code
- tests/fixtures/valid-config.json 4.2 KB
- tests/generator.test.js 5.0 KB runs code
- tests/README.md 557 B
- tests/systems-registry.test.js 2.7 KB runs code
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 · -105 lines · -20 tokens per session 851d67dc2357
- 1mo ago First seen · 134 lines · 55 tokens per session scan A e19e1b55cdfa
multica-platform-apifox is a skill published in the GitHub repository it235/multica-best-practices (212 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 295 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-07.
Other skills, from other repositories
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
enterprise-integration-testing
Use when testing enterprise integrations across SAP, middleware, WMS, or backend systems, validating E2E enterprise flows, testing SAP-specific patterns (RFC, BAPI, IDoc, OData, Fiori), or enforcing cross-system quality gates.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
api-testing
Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients. Covers schema validation with Zod 4/AJV, auth flow testing, CRUD lifecycle tests, error and header validation, pagination, and performance assertions. Use when: "API test," "endpoint test," "REST test," "GraphQL test,"…