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/commands/worktree.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/commands/mock-server/mockserver-monorepo/worktree)<a href="https://agentmods.dev/commands/mock-server/mockserver-monorepo/worktree"><img src="https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/worktree/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/commands/mock-server/mockserver-monorepo/worktree"><img src="https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/worktree.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.00021 | $0.00500 |
| Opus 5.5 | $0.00008 | $0.00200 |
| Sonnet 5.5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
worktree 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
Follow the worktree workflow in .opencode/rules/worktree-workflow.md. This command does Step 1 of that flow:
- Ensure
.worktrees/is gitignored. If not, add.worktrees/to.gitignoreand commit that change to master first. - Pick a short ID:
SHORT_ID="$(date +%Y%m%d-%H%M%S)-$(uuidgen | head -c 6)". - Create the worktree based on the current
origin/master:git fetch origin master --quiet git worktree add --quiet -b "agent/${SHORT_ID}" ".worktrees/agent-${SHORT_ID}" origin/master - Record the worktree path so the session can resume:
mkdir -p .tmp && echo ".worktrees/agent-${SHORT_ID}" > .tmp/active-worktree - Change working directory into the worktree for the rest of the session. All subsequent commands run inside the worktree.
- Tell the user clearly:
- The worktree path.
- That worktree isolation is the default for an independent session: work proceeds inside the worktree, and
git status/git diffis the primary signal. - To merge work back to master, run
/worktree-merge, which runs the 4 verification gates and the locked rebase.
If .tmp/active-worktree already exists, reuse it only if this same session created it (e.g. you are resuming after a restart) — then report that existing path instead of creating a second one. If the pointer may belong to a different concurrent session (you did not create that worktree in this session), do NOT adopt it — create a fresh worktree (new SHORT_ID) with your own branch instead, because two sessions sharing one tree overwrite each other's uncommitted work and can rebase away each other's commits. When ownership is uncertain, create a fresh worktree. See .opencode/rules/worktree-workflow.md → Rule (One session, one worktree — never reuse or adopt another session's).
If the user provided additional instructions: $ARGUMENTS
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 · 26 lines · 21 tokens per session scan A ac24dfedfbc3
worktree is a command published in the GitHub repository mock-server/mockserver-monorepo (4,999 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 500 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-08-30.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
codex-review
Use when asked to check, turn on, turn off, or switch this repo's Codex review mode (local, github, or off), or to report the effective mode and Codex sandbox status.