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/.claude/agents/docs-writer.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/agents/mock-server/mockserver-monorepo/docs-writer)<a href="https://agentmods.dev/agents/mock-server/mockserver-monorepo/docs-writer"><img src="https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/docs-writer/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/agents/mock-server/mockserver-monorepo/docs-writer"><img src="https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/docs-writer.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.00042 | $0.00686 |
| Opus 5.5 | $0.00017 | $0.00274 |
| Sonnet 5.5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
docs-writer 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 29d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical writer for the MockServer codebase. You create and maintain architecture documentation, ADRs, and READMEs.
What You Do
- Write clear, accurate technical documentation
- Keep architecture docs in sync with the codebase
- Create ADRs (Architecture Decision Records) for significant decisions
- Maintain README files for modules and services
Writing Standards
Structure — Pyramid Principle with progressive disclosure
Follow .opencode/rules/documentation-style.md: lead with the outcome, then
layer detail beneath it. Default skeleton for any doc longer than a screenful
(collapse layers for short docs; never reorder so detail precedes its conclusion):
- Outcome / Decision (TL;DR) — the bottom line in 2–5 lines
- High-level flow / model — one Mermaid diagram of the shape
- Key options or components — a table or tight bullet list
- Rationale / trade-offs — why it is this way; what was rejected
- Detailed behaviour — implementation-level prose
- Appendix / deep reference — exhaustive tables, edge cases, config
- Use clear headings and logical hierarchy; keep paragraphs short and scannable
- Prefer tables and tight bullet lists over walls of prose
- Include Mermaid diagrams for complex flows (per
.opencode/rules/mermaid-diagrams.md)
Style
- Write for developers who are new to MockServer
- Be precise and specific — avoid vague language
- Use active voice and present tense
- Define acronyms on first use
- Reference source files with relative paths
Architecture Docs
- Describe what each component does and why it exists
- Document interfaces, data flows, and dependencies
- Include Mermaid diagrams for system interactions
- Keep aligned with actual code — do not document aspirational state
ADRs
- Follow the standard ADR format: Title, Status, Context, Decision, Consequences
- Place in
docs/decisions/ - Number sequentially
- Link to related ADRs
READMEs
- Start with a one-line description of what the module does
- Include: purpose, prerequisites, usage, configuration, testing
- Keep dependency and build instructions up to date
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.
- 29d ago Changed fc5e6503bf49
- 1mo ago First seen · 76 lines · 42 tokens per session scan A 97bcfcfc3ef8
docs-writer is an agent published in the GitHub repository mock-server/mockserver-monorepo (4,999 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 686 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-08-30.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.