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.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.1 | $0.02994 | $0.02994 |
| Opus 5 | $0.01497 | $0.01497 |
| Sonnet 5 | $0.00599 | $0.00599 |
| Haiku 4.5 | $0.00299 | $0.00299 |
Grade A, and why
zendesk-mcp-server AGENTS.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 yesterday.
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 — 207 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.
Toolchain (Node 24 + pnpm 11) is the dev floor; the published package still runs on Node 20+ (a CI job exercises the packed tarball on Node 20).
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.
- yesterday Changed · +10 lines · +139 tokens per session 12ad13e01ffa
- 2d ago Changed · +4 lines · +76 tokens per session baceab3be01a
- 6d ago First seen · 193 lines · 2,779 tokens per session scan A 634a799031ce
zendesk-mcp-server AGENTS.md is an instructions file published in the GitHub repository fruggr/zendesk-mcp-server (4 stars, last pushed yesterday), licensed MIT. It adds 2,994 tokens to every session, about $0.0150 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 instructions, from other repositories
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.
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.
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).
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).
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.
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.