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 emmanuelperu/microcks-skills --skill microcks-import-artifactsgit clone --depth 1 https://github.com/emmanuelperu/microcks-skillsWrote 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/emmanuelperu/microcks-skills/microcks-import-artifacts)<a href="https://agentmods.dev/skills/emmanuelperu/microcks-skills/microcks-import-artifacts"><img src="https://agentmods.dev/badge/skills/emmanuelperu/microcks-skills/microcks-import-artifacts/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/emmanuelperu/microcks-skills/microcks-import-artifacts"><img src="https://agentmods.dev/badge/skills/emmanuelperu/microcks-skills/microcks-import-artifacts.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.00050 | $0.01483 |
| Opus 5 | $0.00025 | $0.00741 |
| Sonnet 5 | $0.00010 | $0.00297 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
microcks-import-artifacts scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
compatibility: Requires Docker and a running Microcks instance (see microcks-local-server skill). Also requires jq and curl. How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microcks Import Artifacts
Import OpenAPI specifications into Microcks and automatically configure dispatchers based on vendor extensions.
When to Use This Skill
Use this skill when:
- Importing an OpenAPI spec into a running Microcks instance for mocking
- Auto-configuring dispatchers after writing a spec with
x-mocking-microcks-dispatcherextensions - Setting up a repeatable import workflow with shell scripts
Prerequisites
- Docker installed and running
- Microcks started (use the
microcks-local-serverskill) - jq installed (
brew install jq/apt install jq) - curl installed
Quick Start
IMPORTANT: The import and dispatcher configuration MUST be done by running the import-openapi.sh shell script. Do NOT attempt to configure dispatchers manually via curl or the Microcks API — the script handles the full workflow (import, discriminant detection, Groovy script loading, API calls).
- Create the
mocking/directory structure:
mkdir -p mocking/dispatchers
- Copy the template scripts into it:
cp templates/import-openapi.sh mocking/import-openapi.sh
cp templates/download-microcks-cli.sh mocking/download-microcks-cli.sh
chmod +x mocking/import-openapi.sh mocking/download-microcks-cli.sh
- Run the import script (this is the only command needed to import AND configure dispatchers):
./mocking/import-openapi.sh path/to/your-api-spec.yaml
The script will:
- Check that Microcks is running
- Download
microcks-cliif not already cached - Import the spec into Microcks
- Read
x-mocking-microcks-dispatchervendor extensions - Auto-configure dispatchers via the Microcks API
Security Notice
This skill provides shell script templates that the user copies into their project. These scripts:
- Download an external binary (
microcks-clifrom GitHub releases of microcks/microcks-cli) - Run Docker containers (
mikefarah/yqfor YAML-to-JSON conversion, from mikefarah/yq) - Make network calls to the local Microcks REST API
What ships with it
2 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.
- 9d ago First seen · 178 lines · 50 tokens per session scan A d255008e358b
microcks-import-artifacts is a skill published in the GitHub repository emmanuelperu/microcks-skills (4 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,483 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
apifox-test-scenario
A guide for building and managing Apifox test scenarios, which are ordered workflows that check how several API calls and other actions work together.
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.
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.
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.
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…