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 skills add stufently/zabbix-ai-cli-mcp --skill zabbix-no-datagit clone --depth 1 https://github.com/stufently/zabbix-ai-cli-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/stufently/zabbix-ai-cli-mcp/zabbix-no-data)<a href="https://agentmods.dev/skills/stufently/zabbix-ai-cli-mcp/zabbix-no-data"><img src="https://agentmods.dev/badge/skills/stufently/zabbix-ai-cli-mcp/zabbix-no-data/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/stufently/zabbix-ai-cli-mcp/zabbix-no-data"><img src="https://agentmods.dev/badge/skills/stufently/zabbix-ai-cli-mcp/zabbix-no-data.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.00047 | $0.00494 |
| Opus 5 | $0.00023 | $0.00247 |
| Sonnet 5 | $0.00009 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
zabbix-no-data 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 12d 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.
What it actually says
Zabbix: silence and no-data
Silence is ambiguous: a host that reports nothing looks the same as a host with nothing wrong. These commands tell the two apart.
Workflow
-
Across the installation:
zabbix-ai-cli-mcp unreachable --jsonLists monitored hosts with an unavailable interface, with the error text Zabbix recorded and whether the host is in maintenance.
-
For one host:
zabbix-ai-cli-mcp host investigate web01 --jsonRead
no_data_itemsandunsupported_itemstogether withstatus.agent_available. -
For specific checks:
zabbix-ai-cli-mcp metrics latest web01 --search disk --jsonEach value carries
no_data,staleandage.
Distinguishing the causes
- Agent unreachable — the interface is unavailable and carries an error. Nothing on that host is reporting; investigate connectivity, not individual checks.
- Item unsupported — the check runs and fails.
errorsays why: a missing binary, a permission problem, a changed key. This is a monitoring fault. - Item silent but supported — the check stopped producing values without erroring. Often a template or interval change.
- In maintenance without data collection — the gap is expected. Check
maintenance listbefore calling it a fault.
Reading the result
stale means the newest value is older than three collection intervals. It is only
computed for items that collect on a schedule: trapper and dependent items arrive
when something else sends or derives them, so silence from one is not a fault.
Items with a flexible or scheduling interval fall back to a conservative threshold
and are not flagged on thin evidence.
Do not
- Do not read
lastclockorlastvaluefrom a rawitem.get. Both have returned a constant zero for several releases, which makes every item look silent.
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.
- 12d ago First seen · 55 lines · 47 tokens per session scan A 841cb4f909ec
zabbix-no-data is a skill published in the GitHub repository stufently/zabbix-ai-cli-mcp (0 stars, last pushed 13d ago), licensed Apache-2.0. It adds 47 tokens to every session and 494 once invoked, about $0.0002 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 skills, from other repositories
host_bash
A read-only shell skill for examining files and running diagnostic commands in a restricted environment. A shell is a text interface for operating-system commands.
host_files
A set of tools for investigating a device’s file system, including finding large files, checking directory disk usage, and inspecting individual files.
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
alert-rule-troubleshoot
This skill should be used when the user reports that an alert rule is "not firing", "no alert was sent", "the rule didn't trigger", "the rule isn't working", "it should have alerted but didn't", "why didn't I get an alert", "alert rule not firing", or wants to diagnose why a specific alert rule failed to produce an…
ops-troubleshooting
This skill should be used when the user asks to "troubleshoot", "diagnose", "debug alert", "investigate incident", "locate a fault", "investigate an alert", "diagnose a problem", "fix an issue", "check alerts", "analyze alerts", "root cause analysis", "check metrics", "check logs", or discusses…
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…