Borrowing it
Nothing to install: this file belongs to fruggr/zendesk-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/fruggr/zendesk-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/fruggr/zendesk-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/fruggr/zendesk-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/fruggr/zendesk-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/fruggr/zendesk-mcp-server/agents-md/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/instructions/fruggr/zendesk-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/fruggr/zendesk-mcp-server/agents-md.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.04389 | $0.04389 |
| Opus 5.5 | $0.01756 | $0.01756 |
| Sonnet 5.5 | $0.00878 | $0.00878 |
| Haiku 4.5 | $0.00439 | $0.00439 |
Grade A, and why
zendesk-mcp-server AGENTS.md scanned grade A 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
exporting, no `curl`: the scripts resolve it themselves (`docs/live-testing.md`). How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Working guide for AI agents
Purpose & scope. This file orients an LLM working in this repo: where things live and the rules that aren't obvious from the code. It is not user documentation.
- Don't document what the code already shows. File-by-file trees, command
listings, env-var tables, setup steps — the agent reads those from the source,
package.jsonor the docs faster than it trusts a prose copy here, and duplicating them only burns context and goes stale. - Keep each section short — durable rules and pointers, not reference material.
When a section grows into setup steps, command listings or exhaustive detail,
it's user-facing (→
README.md) or a deep dive (→docs/): link it, don't inline it. - Write for the next agent, not for the record. A line earns its place here only by changing what someone does next. Don't log what was done, renamed or decided — git history already holds that. Rare exception: a migration still in flight, where both the old and the new state are live; drop the note once it lands.
Toolchain (Node 24 + pnpm 12) is the dev floor; the published package still runs on Node 22+ (a CI job exercises the packed tarball on Node 22).
On Claude Code on the web, the Node environment is set up automatically at session start (dependencies installed), so tests and linters work right away.
Iterating on tool code? Start the server with --dev (stdio) to expose a reload_tools tool. After editing a src/tools/*.ts file, call reload_tools to re-register the whole toolset over the live session — the edit takes effect with no restart and no client reconnect. Details in docs/configuration.md (Dev mode).
Claim before you build — no duplicate work
Parallel duplicate work has happened here. Before coding an issue: re-read it
live (closed completed / released → it already shipped, stop); search open
and merged PRs for its number (is:pr #<n>) — coordinate on an open one,
don't fork; then self-assign, drop a "picking this up" comment, and open your PR
as a draft early. Link the issue in the PR description with a closing keyword
(Closes #<n> — not Implements/bare #<n>, which don't close it) so it
auto-closes on squash-merge to main. Need a follow-up on already-shipped work?
Open a new issue for the delta. Fuller checklist in CONTRIBUTING.md.
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.
- today Changed · +16 lines · +193 tokens per session c9e4cdabf064
- 4d ago Changed · +9 lines · +163 tokens per session 4be76996104f
- 7d ago Changed · +2 lines · +33 tokens per session 4292c3f3719f
- 8d ago Changed · -1 lines · -3 tokens per session dd3cca4d00b2
- 21d ago Changed · +3 lines · +70 tokens per session e06c20523193
- 25d ago Changed · +5 lines · +96 tokens per session df6105bf6af8
- 29d ago Changed · +14 lines · +211 tokens per session 7d16adced8cd
- 1mo ago Changed · +7 lines · +119 tokens per session be4fa1abdf69
- 1mo ago Changed · +4 lines · +92 tokens per session 7cabb87b74a8
- 1mo ago First seen · 238 lines · 3,415 tokens per session scan A 701868379991
zendesk-mcp-server AGENTS.md is an instructions file published in the GitHub repository fruggr/zendesk-mcp-server (14 stars, last pushed today), licensed MIT. It adds 4,389 tokens to every session, about $0.0176 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.