Borrowing it
Nothing to install: this file belongs to basher83/Zammad-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.
curl -O https://raw.githubusercontent.com/basher83/Zammad-MCP/main/.codex/skills/zammad-mcp-issue-digest/SKILL.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/skills/basher83/zammad-mcp/zammad-mcp-issue-digest)<a href="https://agentmods.dev/skills/basher83/zammad-mcp/zammad-mcp-issue-digest"><img src="https://agentmods.dev/badge/skills/basher83/zammad-mcp/zammad-mcp-issue-digest/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/skills/basher83/zammad-mcp/zammad-mcp-issue-digest"><img src="https://agentmods.dev/badge/skills/basher83/zammad-mcp/zammad-mcp-issue-digest.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.00061 | $0.01630 |
| Opus 5 | $0.00030 | $0.00815 |
| Sonnet 5 | $0.00012 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
zammad-mcp-issue-digest 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 9d 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 ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 251 B
- scripts/collect_issue_digest.py 35 KB runs code
- scripts/post_triage_digest.py 8.6 KB runs code
- scripts/test_collect_issue_digest.py 6.5 KB runs code
- scripts/test_triage_issue.py 8.6 KB runs code
- scripts/triage_common.py 24 KB runs code
- scripts/triage_issue.py 4.6 KB runs code
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.
- 9d ago First seen · 125 lines · 61 tokens per session scan A 81949a7b0ac5
zammad-mcp-issue-digest is a skill published in the GitHub repository basher83/Zammad-MCP (38 stars, last pushed today), licensed AGPL-3.0. It adds 61 tokens to every session and 1,630 once invoked, about $0.0003 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 skills, from other repositories
Zendesk Automation
Automate customer support workflows with Zendesk ticket management, routing, and analytics.
inbox-triage
Triage and prioritize open support conversations by reviewing unassigned tickets, identifying urgent issues, and suggesting agent assignments based on workload. Use when the user asks to review their inbox, triage conversations, check what needs attention, handle unassigned tickets, balance workload, or see what is…
team-workload
Analyze team capacity and workload distribution — see who is overloaded, who has bandwidth, and rebalance conversation assignments across the team. Use when the user asks about team capacity, workload, agent availability, or wants to redistribute work.
contact-onboard
Onboard a new contact into the support system by checking for duplicates, creating their profile, and adding contextual notes. Use when the user wants to add a new customer, create a contact, register a lead, onboard someone into the CRM, or mentions a new person they want to track.
daily-briefing
Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…