Borrowing it
Nothing to install: this file belongs to garoon/garoon-mcp-server. 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/garoon/garoon-mcp-server/main/.claude/skills/smoke-test-mcp-tools/SKILL.mdgit clone --depth 1 https://github.com/garoon/garoon-mcp-serverWrote 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/garoon/garoon-mcp-server/smoke-test-mcp-tools)<a href="https://agentmods.dev/skills/garoon/garoon-mcp-server/smoke-test-mcp-tools"><img src="https://agentmods.dev/badge/skills/garoon/garoon-mcp-server/smoke-test-mcp-tools/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/garoon/garoon-mcp-server/smoke-test-mcp-tools"><img src="https://agentmods.dev/badge/skills/garoon/garoon-mcp-server/smoke-test-mcp-tools.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.00096 | $0.01449 |
| Opus 5 | $0.00048 | $0.00724 |
| Sonnet 5 | $0.00019 | $0.00290 |
| Haiku 4.5 | $0.00010 | $0.00145 |
Grade A, and why
smoke-test-mcp-tools 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 10d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Garoon MCP tool smoke test
Purpose
Verify that every tool of the Garoon MCP server under development executes without
error against a live Garoon environment. For each tool, the agent derives a
sample-prompt-equivalent input, actually invokes the corresponding mcp__garoon__*
tool, and judges the result. This is a live smoke test (real API calls), not a
static argument-validation check.
Prerequisites
.envrc(gitignored) exportsGAROON_BASE_URL,GAROON_USERNAME,GAROON_PASSWORD, and any optional variables (proxy, PFX, basic auth,GAROON_PUBLIC_ONLY). See CONTRIBUTING.md for the setup.- direnv has loaded those variables into the
claudeprocess environment (direnv allowwas run andclaudewas started from the repository root). dist/is up to date (pnpm run build).- The
garoonserver from.mcp.jsonis connected in Claude Code (claude mcp listshowsgaroonas✔ Connected).
Changing .mcp.json, env vars, or the build usually requires reconnecting
(restarting the Claude Code session). If no mcp__garoon__* tools are visible,
satisfy the prerequisites above and reconnect before retrying.
Procedure
Step 0: Readiness check
- Confirm
dist/is current; runpnpm run buildif unsure. - Enumerate the available
mcp__garoon__*tools. If none exist, return to the prerequisites. - Do not hardcode the tool list. Target whatever
mcp__garoon__*tools are enumerable at runtime, so newly added tools are covered without editing this skill.
Sample-prompt generation
For each tool, derive one natural sample prompt from its title / description /
inputSchema, record it in the report, and call the tool with arguments that
satisfy that intent (e.g. garoon-get-current-time → "What is the current time in
Garoon?").
Dependency-aware execution order
Some tools require IDs returned by other tools. Execute in the phases below, and
infer dependencies from each tool's input field names (e.g. if organizationId
is required, collect an organization ID first).
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.
- 10d ago First seen · 127 lines · 96 tokens per session scan A dd897b6fcf82
smoke-test-mcp-tools is a skill published in the GitHub repository garoon/garoon-mcp-server (7 stars, last pushed 4d ago), licensed Apache-2.0. It adds 96 tokens to every session and 1,449 once invoked, about $0.0005 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-31.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…