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-local-servergit 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-local-server)<a href="https://agentmods.dev/skills/emmanuelperu/microcks-skills/microcks-local-server"><img src="https://agentmods.dev/badge/skills/emmanuelperu/microcks-skills/microcks-local-server/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-local-server"><img src="https://agentmods.dev/badge/skills/emmanuelperu/microcks-skills/microcks-local-server.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.00054 | $0.00954 |
| Opus 5 | $0.00027 | $0.00477 |
| Sonnet 5 | $0.00011 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
microcks-local-server 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.
until curl -s -o /dev/null http://localhost:8080/api; do How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microcks Local Server
Set up and run a local Microcks server using Docker Compose for API mocking and testing.
When to Use
- A developer wants to mock a REST API locally from an OpenAPI specification
- A project needs a local API mock server for development or integration testing
- Someone asks to "start Microcks", "run a mock server", or "set up API mocking"
Prerequisites
- Docker and Docker Compose installed and running
Start the Server
- Create a
mocking/directory at the project root (if it doesn't exist):
mkdir -p mocking
- Copy the Docker Compose template from templates/docker-compose.yml into it:
cp templates/docker-compose.yml mocking/docker-compose.yml
- Start the containers:
# From the project root
docker compose -f mocking/docker-compose.yml up -d
# Or from the mocking/ directory
cd mocking && docker compose up -d
- Wait for Microcks to be ready:
until curl -s -o /dev/null http://localhost:8080/api; do
echo "Waiting for Microcks to be up..."
sleep 3
done
echo "Microcks is ready!"
Verify the Server
- Health check:
curl -s http://localhost:8080/api - Web console: open
http://localhost:8080in a browser - List services:
curl -s http://localhost:8080/api/services
Stop the Server
When confirming the server is running, ALWAYS remind the user they can stop it by asking "stop the Microcks server" or by running docker compose -f mocking/docker-compose.yml down.
# From the project root
docker compose -f mocking/docker-compose.yml down
# Or from the mocking/ directory
cd mocking && docker compose down
Configuration Details
| Setting | Value | Notes |
|---|---|---|
| Microcks image | quay.io/microcks/microcks:1.13.2 |
Pinned stable version |
| MongoDB image | mongo:7.0 |
LTS version |
| Microcks port | 8080 |
REST API and web console |
| MongoDB port | 27017 |
Exposed for debugging, not required |
| Authentication | Disabled | KEYCLOAK_ENABLED=false, no login needed |
| Storage | Ephemeral | Data is lost when containers stop |
What ships with it
1 file 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 · 122 lines · 54 tokens per session scan A c719f2c0c5a1
microcks-local-server is a skill published in the GitHub repository emmanuelperu/microcks-skills (4 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 954 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.
explore-api
Explore an OpenAPI spec's structure using parse and walk tools.
diff-specs
Compare two OpenAPI spec versions, highlight breaking changes, and suggest migration steps.
fix-spec
Auto-fix common OpenAPI spec issues with a preview-first workflow.
generate-code
Generate Go client, server, or type code from an OpenAPI spec.
validate-spec
Validate an OpenAPI spec, explain errors clearly, and suggest or apply fixes.