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 commands/basher83/zammad-mcp/git_commitgit clone --depth 1 https://github.com/basher83/Zammad-MCPWhat 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.00026 | $0.00232 |
| Opus 5 | $0.00013 | $0.00116 |
| Sonnet 5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
git_commit 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 2d 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.
- 2d ago First seen · 25 lines · 26 tokens per session scan A 5438b848517f
git_commit is a command published in the GitHub repository basher83/Zammad-MCP (38 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 26 tokens to every session and 232 once invoked, about $0.0001 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 commands, from other repositories
report
Generate a weekly support performance report with KPIs, team rankings, channel breakdown, and AI automation stats. Run this for your weekly standup or executive summary.
signup
Create a brand-new Corebee account from your terminal — one email approval, then a scoped API key + a live chat-widget snippet. Use when you don't have a Corebee account yet.
kb-status
Check the health of your AI knowledge base — shows indexed sources, pending items, errors, and coverage gaps. Run this to audit what your AI knows.
triage
Triage the support inbox — shows urgent conversations, stale tickets, and suggests assignments. Run this to quickly see what needs attention.
make-agent-ready
Make a provider's API agent-ready — comprehend its OpenAPI/docs with gecko, serve the FULL surface over MCP with a one-click add, emit the discovery breadcrumbs, and leave the provider's own MCP intact. Usage: /make-agent-ready.
setup-x402
Wire x402 pay-per-call onto a provider's already-comprehended API via PayAI — point tools at the provider's OWN x402 endpoint, prove the handshake offline (X402MODE=stub), keep the provider at 100%. Gecko never the rail, no cut. Usage: /setup-x402.