mockserver-monorepo: Command for Claude Code

.claude/commands/aws-investigation.md

aws-investigation is a command for Claude Code from mock-server/mockserver-monorepo. It costs 10 tokens per session (66 once invoked), scanned A, original, Apache-2.0.

A command that starts an AWS infrastructure investigation for Buildkite build agents.

In plain words
What is it for?
Use it when Buildkite agents are not running or when EC2, Auto Scaling, or other AWS infrastructure may be responsible.
Why use it?
It routes infrastructure problems to a dedicated investigation process instead of treating them as ordinary build failures.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents; mentions OpenCode.

This is mock-server/mockserver-monorepo's own configuration. It tells Claude Code how to work on mockserver-monorepo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mockserver-monorepo configures →

About the project

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.

mock-server/mockserver-monorepo · 4,967 stars · on GitHub · mock-server.com

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/mock-server/mockserver-monorepo/master/.claude/commands/aws-investigation.md
Clone the repo
git clone --depth 1 https://github.com/mock-server/mockserver-monorepo

Made for: Claude Code.

Wrote 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.

agentmods badge for aws-investigation

README.md
[![agentmods](https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/aws-investigation.svg)](https://agentmods.dev/commands/mock-server/mockserver-monorepo/aws-investigation)
Your own site
<a href="https://agentmods.dev/commands/mock-server/mockserver-monorepo/aws-investigation"><img src="https://agentmods.dev/badge/commands/mock-server/mockserver-monorepo/aws-investigation.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 66 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00066
Opus 5 $0.00005 $0.00033
Sonnet 5 $0.00002 $0.00013
Haiku 4.5 $0.00001 $0.00007

Measured 8d ago against content hash 9200052ed798, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

aws-investigation 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 8d 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.

.claude/commands/aws-investigation.md · 9 lines

What it actually says

Use the Agent tool to spawn a debugger subagent to investigate AWS infrastructure for the following request:

$ARGUMENTS

The debugger agent should read .opencode/skills/aws-investigation/SKILL.md and follow its investigation workflow.

Changes

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.

  1. 8d ago First seen · 9 lines · 10 tokens per session scan A 9200052ed798

Subscribe to this mod's changes

aws-investigation is a command published in the GitHub repository mock-server/mockserver-monorepo (4,967 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 66 once invoked, about $0.0001 per session on Opus 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.