Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/gleanwork/mcp-server-tester/write-mcp-testnpx skills add gleanwork/mcp-server-tester --skill write-mcp-testgit clone --depth 1 https://github.com/gleanwork/mcp-server-testerWrote 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/gleanwork/mcp-server-tester/write-mcp-test)<a href="https://agentmods.dev/skills/gleanwork/mcp-server-tester/write-mcp-test"><img src="https://agentmods.dev/badge/skills/gleanwork/mcp-server-tester/write-mcp-test.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.02322 |
| Opus 5 | $0.00026 | $0.01161 |
| Sonnet 5 | $0.00010 | $0.00464 |
| Haiku 4.5 | $0.00005 | $0.00232 |
Grade A, and why
write-mcp-test 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 5d 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write MCP Server Tests
Generate Playwright tests for MCP server tools using @gleanwork/mcp-server-tester.
Before You Start
- Confirm the project has
@gleanwork/mcp-server-testerand@playwright/testinstalled - Check that
playwright.config.tshasmcpConfigin at least one project'suseblock - Identify which MCP tools to test — run
mcp.listTools()or check the server's tool definitions
Step 1 — Verify Playwright Config
Every test project needs an mcpConfig entry. If it doesn't exist, add one:
// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
testDir: './tests',
projects: [
{
name: 'my-mcp-server',
use: {
mcpConfig: {
// stdio transport — for servers started as a subprocess
transport: 'stdio',
command: 'node',
args: ['./dist/server.js'],
},
// OR http transport — for servers already running
// mcpConfig: {
// transport: 'http',
// url: 'http://localhost:3000/mcp',
// },
},
},
],
});
Step 2 — Create Test File
Always import test and expect from the fixtures path:
import { test, expect } from '@gleanwork/mcp-server-tester/fixtures/mcp';
Do NOT import from @gleanwork/mcp-server-tester — that path does not include MCP matchers on expect.
Step 3 — Write Tests
Basic tool test
import { test, expect } from '@gleanwork/mcp-server-tester/fixtures/mcp';
test.describe('search tool', () => {
test('returns results for a valid query', async ({ mcp }) => {
const result = await mcp.callTool('search', {
query: 'quarterly planning',
});
expect(result).toContainToolText('quarterly');
expect(result).not.toBeToolError();
});
test('handles empty query gracefully', async ({ mcp }) => {
const result = await mcp.callTool('search', { query: '' });
// Assert it returns an error or empty result — not a crash
expect(result).not.toBeToolError();
});
});
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.
- 5d ago First seen · 323 lines · 52 tokens per session scan A bc16beb83175
write-mcp-test is a skill published in the GitHub repository gleanwork/mcp-server-tester (19 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 2,322 once invoked, about $0.0003 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.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
agent-device-evidence
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR.