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 aspectrr/deer --skill kibana-alerting-rulesgit clone --depth 1 https://github.com/aspectrr/deerWrote 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/aspectrr/deer/kibana-alerting-rules)<a href="https://agentmods.dev/skills/aspectrr/deer/kibana-alerting-rules"><img src="https://agentmods.dev/badge/skills/aspectrr/deer/kibana-alerting-rules/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/aspectrr/deer/kibana-alerting-rules"><img src="https://agentmods.dev/badge/skills/aspectrr/deer/kibana-alerting-rules.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.00048 | $0.01750 |
| Opus 5 | $0.00024 | $0.00875 |
| Sonnet 5 | $0.00010 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
kibana-alerting-rules scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "https://my-kibana:5601/api/alerting/rule/my-rule-id" \ How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kibana Alerting Rules
Core Concepts
A rule has three parts: conditions (what to detect), schedule (how often to check), and actions (what happens when conditions are met). When conditions are met, the rule creates alerts, which trigger actions via connectors.
Authentication
All alerting API calls require either API key auth or Basic auth. Every mutating request must include the kbn-xsrf
header.
kbn-xsrf: true
API Reference
Base path: <kibana_url>/api/alerting (or /s/<space_id>/api/alerting for non-default spaces).
| Operation | Method | Endpoint |
|---|---|---|
| Create rule | POST | /api/alerting/rule/{id} |
| Update rule | PUT | /api/alerting/rule/{id} |
| Get rule | GET | /api/alerting/rule/{id} |
| Delete rule | DELETE | /api/alerting/rule/{id} |
| Find rules | GET | /api/alerting/rules/_find |
| List rule types | GET | /api/alerting/rule_types |
| Enable rule | POST | /api/alerting/rule/{id}/_enable |
| Disable rule | POST | /api/alerting/rule/{id}/_disable |
| Mute all alerts | POST | /api/alerting/rule/{id}/_mute_all |
| Unmute all alerts | POST | /api/alerting/rule/{id}/_unmute_all |
Creating a Rule
Required Fields
| Field | Type | Description |
|---|---|---|
name |
string | Display name (does not need to be unique) |
rule_type_id |
string | The rule type (e.g., .es-query, .index-threshold) |
consumer |
string | Owning app: alerts, apm, discover, infrastructure, logs, metrics, ml, monitoring, securitySolution, siem, stackAlerts, uptime |
params |
object | Rule-type-specific parameters |
schedule |
object | Check interval, e.g., {"interval": "5m"} |
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 · 167 lines · 48 tokens per session scan A 5f6fe4050ee4
kibana-alerting-rules is a skill published in the GitHub repository aspectrr/deer (404 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,750 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
skypilot-multi-cloud-orchestration
Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.
lambda-gpu-cloud
Safely inspect and operate Lambda Cloud GPU instances through the documented Cloud API and SSH, with explicit approval before billable or destructive actions.
modal-serverless-gpu
Run approved CPU or GPU work through OpenScience computejob on the user's configured Modal account. Use for isolated scientific scripts, dependency provisioning, durable outputs, logs, status, cancellation, and recovery. Never invoke the Modal SDK or CLI directly.
runpod-gpu-cloud
Safely inspect and operate RunPod resources with runpodctl, live product data, and explicit approval before paid or destructive actions.
tensorpool-gpu-cloud
Safely inspect and operate TensorPool GPU clusters and jobs using the current tp CLI, with explicit approval before any billable or destructive action.
vast-ai-gpu-cloud
Safely inspect and operate Vast.ai marketplace instances with the vastai CLI, live offer data, and explicit approval before paid or destructive actions.