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 instructions/milo0821/zephyr_mcp_server/claude-mdgit clone --depth 1 https://github.com/Milo0821/Zephyr_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/instructions/milo0821/zephyr_mcp_server/claude-md)<a href="https://agentmods.dev/instructions/milo0821/zephyr_mcp_server/claude-md"><img src="https://agentmods.dev/badge/instructions/milo0821/zephyr_mcp_server/claude-md.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.01674 | $0.01674 |
| Opus 5 | $0.00837 | $0.00837 |
| Sonnet 5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade B, and why
Zephyr_mcp_server CLAUDE.md scanned grade B with 1 finding 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
npm run build # tsc + chmod 755 build/index.js How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zephyr Scale MCP Server
Project Overview
A Model Context Protocol (MCP) server that bridges AI assistants to Zephyr Scale test case management. It supports both Jira Cloud and Jira Data Center, exposing tools and resources for creating, reading, and managing test cases, test runs, and test executions via the Atlassian REST API.
Published to npm as zephyr-scale-mcp-server (v0.3.2).
Architecture
src/
├── index.ts # MCP server entry point — wires transport, tools, resources
├── tool-handlers.ts # ZephyrToolHandlers class — all tool implementations
├── tool-schemas.ts # MCP tool input schemas (JSON Schema)
├── resources.ts # MCP resource handlers (file://, zephyr://testcase/, zephyr://examples/)
├── types.ts # TypeScript interfaces (TestCaseArgs, JiraConfig, etc.)
└── utils.ts # Jira config, BDD→Gherkin conversion, API endpoint routing
build/ # Compiled output (ES2022, Node16 modules) — committed to repo
test/
├── run-tests.cjs # Main test runner (unit + integration)
├── zephyr-server.test.cjs # Unit tests
└── integration.test.cjs # Integration tests (require live env vars)
scripts/
└── weekly-report.cjs # Standalone weekly report script
Module system: The server uses ES modules ("type": "module" in package.json); test files use .cjs extension to stay CommonJS.
Build & Run
npm run build # tsc + chmod 755 build/index.js
npm start # node build/index.js
npm run watch # tsc --watch
npm run inspector # MCP inspector UI
Always run npm run build after editing src/ — the build/ directory is what gets published and executed.
Testing
npm test # unit + integration (needs env vars for integration)
npm run test:unit # unit tests only — no env vars required
npm run test:integration
Unit tests check: package config, build artifacts, environment variables, server startup, tool registration.
Integration tests require at minimum ZEPHYR_BASE_URL to be set.
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.
- 4d ago First seen · 158 lines · 1,674 tokens per session scan B 8e70bedd1251
Zephyr_mcp_server CLAUDE.md is an instructions file published in the GitHub repository Milo0821/Zephyr_mcp_server (5 stars, last pushed 3mo ago), licensed MIT. It adds 1,674 tokens to every session, about $0.0084 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.