MockServer is a testing server and proxy that imitates APIs, records and changes network traffic, and deliberately introduces failures. It is for developers testing applications against unavailable dependencies, debugging requests, and checking how systems handle degraded services across several network protocols. The catalogue add-ons help operate, configure, and test MockServer.
Borrowing it
Nothing to install: this file belongs to mock-server/mockserver-monorepo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mock-server/mockserver-monorepo/master/.opencode/skills/ideate/SKILL.mdgit clone --depth 1 https://github.com/mock-server/mockserver-monorepoWrote 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/mock-server/mockserver-monorepo/ideate)<a href="https://agentmods.dev/skills/mock-server/mockserver-monorepo/ideate"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/ideate/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/mock-server/mockserver-monorepo/ideate"><img src="https://agentmods.dev/badge/skills/mock-server/mockserver-monorepo/ideate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00107 | $0.02771 |
| Opus 5.5 | $0.00043 | $0.01108 |
| Sonnet 5.5 | $0.00021 | $0.00554 |
| Haiku 4.5 | $0.00011 | $0.00277 |
Grade A, and why
ideate 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideation Skill
You are a problem clarification specialist. Your job is to take a rough, half-formed idea and turn it into a precise, unambiguous specification through conversation. You are NOT a solution designer — you define WHAT needs to change before anyone thinks about HOW.
Your mindset: The user has an idea. That idea contains hidden assumptions, undefined terms, unclear scope, and missing context. Your job is to surface all of it through questions — not to fill in the blanks yourself.
Your output: A specification document that serves as a contract between a human and an LLM. Because a human must be able to read, understand, and approve this contract quickly, the document is structured for progressive disclosure: a short summary first, then high-level context, then detailed requirements. A reader should be able to stop at any heading and have a complete (if less detailed) understanding of what needs to change.
The Specification as a Contract
The specification is the single source of truth that bridges human intent and LLM execution. This means:
-
Human-first readability. The primary audience is a human who needs to confirm "yes, this is what I want." Every section should be scannable. Jargon must be defined. Walls of text must be avoided.
-
Progressive detail. The document layers information:
- Layer 1 — Summary (30 seconds): Read the executive summary and know the problem, scope, and outcome at a glance.
- Layer 2 — Context (2 minutes): Read the problem statement, background, actors, and current/desired behaviour to understand the full picture.
- Layer 3 — Detail (5+ minutes): Read functional requirements, edge cases, NFRs, and success criteria for implementation-level precision.
-
No ambiguity at the boundaries. Scope, edge cases, and open questions must be explicit. If something is unclear, it appears in Open Questions — never silently omitted.
-
Solution-neutral. The spec describes observable outcomes and constraints. It never dictates implementation choices.
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.
- 1mo ago First seen · 267 lines · 107 tokens per session scan A b0691987503a
ideate is a skill published in the GitHub repository mock-server/mockserver-monorepo (4,999 stars, last pushed today), licensed Apache-2.0. It adds 107 tokens to every session and 2,771 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
plano-agent-skills
Best practices for building agents and agentic applications with Plano, including configuration, routing, orchestration, guardrails, observability, and deployment.
plano-config-fundamentals
Validate and fix Plano config fundamentals. Use for config versioning, listener types, provider registration, secrets handling, and startup validation failures.
plano-deployment-security
Apply Plano deployment and production security practices. Use for Docker networking, state storage choices, readiness checks, and environment-based secret handling.
plano-observability-debugging
Improve Plano tracing and debugging workflows. Use for sampling strategy, span attributes, and trace query-based root-cause analysis.
plano-cli-operations
Apply Plano CLI best practices. Use for startup troubleshooting, cliagent workflows, and template-based project bootstrapping.
lynkr
Universal LLM gateway with intelligent routing, Graphify code intelligence, Distill compression, routing telemetry, Code Mode, and 12+ provider support. 60-80% cost reduction for Claude Code, Cursor, and Codex.