zapi-mcp: Instructions file for GitHub Copilot

.github/copilot-instructions.md

zapi-mcp copilot-instructions.md is an instructions file for GitHub Copilot from shigechika/zapi-mcp. It costs 2,517 tokens per session, scanned A, original, MIT.

Project instructions for reviewing zapi-mcp, a server that exposes Zabbix monitoring data to AI assistants. They describe the repository, validation commands, review priorities, security concerns, and test conventions.

In plain words
What is it for?
Use them when reviewing changes to the Zabbix server, categories, API client integration, tests, CI checks, or security-sensitive tool behavior.
Why use it?
They help reviewers check real failure risks, including unsafe tool inputs, authentication, pagination, and standard build or test requirements.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: mentions CLAUDE.md.

This is shigechika/zapi-mcp's own configuration. It tells GitHub Copilot how to work on zapi-mcp 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 zapi-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to shigechika/zapi-mcp. 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/shigechika/zapi-mcp/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/shigechika/zapi-mcp

Made for: GitHub Copilot.

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 zapi-mcp copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/shigechika/zapi-mcp/copilot-instructions/github.svg)](https://agentmods.dev/instructions/shigechika/zapi-mcp/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/shigechika/zapi-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/shigechika/zapi-mcp/copilot-instructions/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.

agentmods 80×15 button for zapi-mcp copilot-instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/shigechika/zapi-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/shigechika/zapi-mcp/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,517 This file is loaded in full into every session.
When invoked 2,517 The same file — it is already loaded in full.
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.02517 $0.02517
Opus 5.5 $0.01007 $0.01007
Sonnet 5.5 $0.00503 $0.00503
Haiku 4.5 $0.00252 $0.00252

Measured 13d ago against content hash 03c5d05b1fe3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zapi-mcp copilot-instructions.md 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 13d 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.

.github/copilot-instructions.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository overview

zapi-mcp is an MCP (Model Context Protocol) server exposing the Zabbix API (active problems, hosts, item values, a daily_brief morning-patrol summary) to AI assistants over stdio transport. Built on the official mcp Python SDK's MCPServer (zapi_mcp/server.py). The actual Zabbix HTTP client (ZapiClient, auth, pagination) lives in the separate zapi-lib package; zapi_mcp/client.py is only a backward-compatible re-export shim.

See CLAUDE.md for the authoritative command list and architecture notes — read it before reviewing changes to server.py or categories.py.

Build & validate

uv sync --dev
uv run pytest -v                    # all tests
uv run ruff check .                 # lint
uv run ruff format --check .        # format check

This mirrors .github/workflows/ci.yml: a lint job (ruff check + ruff format --check) and a separate test job (pytest -v) on Python 3.10/3.12/3.13 on Linux, plus one Windows 3.12 job specifically to catch stdio newline regressions (modelcontextprotocol/python-sdk#2433). Both lint and test are real CI gates here — unlike some sibling MCP repos in this family, don't assume lint is unenforced.

What to focus review on in this repo

1. This is a stdio MCP server — stdout is a JSON-RPC channel, not a log

Any print() or library logging that writes to stdout (instead of stderr) corrupts the protocol stream for the connected client. As of now this codebase has no logging usage at all, and every print() call in __main__.py sits in a branch that calls sys.exit() before mcp.run() is reached — the --version branch, the missing-env-var check, and the --check / --brief branches — so none of them ever run concurrently with the live stdio server. Flag any new code path that adds a print(), or a logger without an explicit stderr handler, that could execute while mcp.run() is active — that would be a new failure mode, not a fix to an existing one.

2. MCPServer already wraps tool returns — don't ask for manual envelope code

Read the full file on GitHub · 168 lines

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. 13d ago Changed · +18 tokens per session 03c5d05b1fe3
  2. 28d ago Changed · -1 tokens per session 2dad655ba4db
  3. 1mo ago First seen · 168 lines · 2,500 tokens per session scan A 0574f99f561f

Subscribe to this mod's changes

zapi-mcp copilot-instructions.md is an instructions file published in the GitHub repository shigechika/zapi-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 2,517 tokens to every session, about $0.0101 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-31.

Related

Other instructions, from other repositories