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/basher83/zammad-mcp/claude-mdgit clone --depth 1 https://github.com/basher83/Zammad-MCPWrote 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/basher83/zammad-mcp/claude-md)<a href="https://agentmods.dev/instructions/basher83/zammad-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/basher83/zammad-mcp/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.00003 | $0.00003 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
Zammad-MCP CLAUDE.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 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 1 lines · 3 tokens per session scan A a54ff182c7e8
Zammad-MCP CLAUDE.md is an instructions file published in the GitHub repository basher83/Zammad-MCP (38 stars, last pushed yesterday), licensed AGPL-3.0. It adds 3 tokens to every session, about $0.0000 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 instructions, from other repositories
support-mcp CLAUDE.md
Claude Code instructions for tehprof/support-mcp, covering support mcp server — claude.md, ⛔ глобальные правила (подробности → /srv/claude.md), назначение, stack and структура.
pinmeto-location-mcp AGENTS.md
AGENTS.md instructions for PinMeTo/pinmeto-location-mcp, covering agent instructions, project overview, environment configuration, releases and changesets and feature development workflow.
pinmeto-location-mcp CLAUDE.md
Claude Code instructions for PinMeTo/pinmeto-location-mcp, covering claude.md and project documentation.
mcp-freescout AGENTS.md
AGENTS.md instructions for verygoodplugins/mcp-freescout, covering agents.md, repository purpose, common commands, project conventions and layout.
mcp-freescout CLAUDE.md
Claude Code instructions for verygoodplugins/mcp-freescout, a project described as: An MCP (Model Context Protocol) server for FreeScout helpdesk ticket management and workflow automation. This server provides tools to interact with FreeScout tickets, analyze issues, manage responses, and integrate with Git workflows.
liquid CLAUDE.md
Claude Code instructions for ertad-family/liquid, covering liquid, project overview, tech stack, project structure and development commands.