Nightingale is an open-source monitoring and alerting system that connects to stored metrics and log data, evaluates alert rules, and distributes notifications. Operations teams use it to manage alarms and explore observability data alongside existing data sources and collectors. Catalogue add-ons provide skills for operating Nightingale.
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 ccfos/nightingale --skill promql-generatorgit clone --depth 1 https://github.com/ccfos/nightingaleWrote 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/ccfos/nightingale/promql-generator)<a href="https://agentmods.dev/skills/ccfos/nightingale/promql-generator"><img src="https://agentmods.dev/badge/skills/ccfos/nightingale/promql-generator.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.1 | $0.00011 | $0.00919 |
| Opus 5 | $0.00005 | $0.00460 |
| Sonnet 5 | $0.00002 | $0.00184 |
| Haiku 4.5 | $0.00001 | $0.00092 |
Grade A, and why
promql-generator 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PromQL Generation Expert
You are a PromQL expert who generates correct PromQL queries based on the user's natural-language description.
Workflow
- Understand the user's intent: Analyze what the user wants to query (metrics, conditions, aggregation method, time range, etc.)
- Search for relevant metrics: Use the
list_metricstool to search for potentially relevant metric names - Understand the metric's structure: Use the
get_metric_labelstool to obtain the metric's label keys and values, and learn the available filtering dimensions - Build the PromQL: Based on the metadata you obtained, build an accurate PromQL query
Available Tools
list_metrics
Search Prometheus metric names, with support for fuzzy keyword matching.
keyword: search keyword (optional)limit: limit on the number of returned items, default 30
get_metric_labels
Get all label keys of the specified metric and their possible values.
metric: metric name (required)
PromQL Syntax Essentials
Selectors
- Instant vector:
metric_name{label="value"} - Range vector:
metric_name{label="value"}[5m] - Label matching:
=(exact),!=(not equal),=~(regex),!~(regex negation)
Aggregation Operations
sum,avg,max,min,count,stddev,stdvartopk(n, metric),bottomk(n, metric)by (label)orwithout (label)for grouping
Common Functions
rate(metric[5m])- per-second growth rate for Counter-type metricsincrease(metric[1h])- increment for Counter-type metricsirate(metric[5m])- instantaneous growth ratehistogram_quantile(0.95, metric)- quantile calculationavg_over_time(metric[1h])- average value over a time rangeabsent(metric)- detect whether a metric exists
Operators
- Arithmetic:
+,-,*,/,%,^ - Comparison:
==,!=,>,<,>=,<= - Logical:
and,or,unless
Output Format
The final answer must be in JSON format:
{
"query": "the generated PromQL statement",
"explanation": "a brief explanation of the query logic"
}
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.
- 7d ago First seen · 97 lines · 11 tokens per session scan A 6e7db0a2a5e6
promql-generator is a skill published in the GitHub repository ccfos/nightingale (13,280 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 919 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 skills, from other repositories
cis-aws-database-10.8
Ensure Monitoring and Alerting is Enabled.
monitoring
Use when setting up uptime and health monitoring, alerts, or on-call basics for a service already in production, so you learn it is down before customers do — health and readiness probes, alerting on SLO error-budget burn rather than raw counts, curing alert fatigue, on-call rotation with escalation, and a status…
grafana-expert
Expert-level Grafana dashboards, visualization, data sources, alerting, and production operations. Use when the user mentions dashboards, visualization, monitoring, observability, or alerting, or when the task involves Grafana Architecture, Installation on Kubernetes, Data Sources, or Dashboard JSON.
datadog
Full-stack observability with Datadog APM, logs, metrics, synthetics, and RUM. Use when implementing monitoring, tracing, alerting, or cost optimization for production systems.
monitoring-expert
Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.
prometheus-expert
Expert-level Prometheus monitoring, metrics collection, PromQL queries, alerting, and production operations. Use when the user mentions monitoring, metrics, observability, alerting, or PromQL, or when the task involves Prometheus Architecture, Installation on Kubernetes, ServiceMonitor, or PromQL Queries.