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 generate-message-templategit 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/generate-message-template)<a href="https://agentmods.dev/skills/ccfos/nightingale/generate-message-template"><img src="https://agentmods.dev/badge/skills/ccfos/nightingale/generate-message-template/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/ccfos/nightingale/generate-message-template"><img src="https://agentmods.dev/badge/skills/ccfos/nightingale/generate-message-template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.05258 |
| Opus 5.5 | $0.00024 | $0.02103 |
| Sonnet 5.5 | $0.00012 | $0.01052 |
| Haiku 4.5 | $0.00006 | $0.00526 |
Grade A, and why
generate-message-template 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 1mo 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nightingale (n9e) Notification Message Template Generation
Nightingale message templates use Go text/template / html/template syntax (email uses text/template, others use html/template and then escape). Users edit them on the "Notification Management → Message Templates" page; once saved they are referenced by notification rules, and when an alert fires the variables are substituted with rendered data and sent to each channel.
This skill focuses on writing/modifying the template fragment itself, and does not cover creating notification rules or channel configuration.
Render Context
The renderData passed in when the backend executes:
| key | type | description |
|---|---|---|
.events |
[]*AlertCurEvent |
The list of alert events in the current batch, usually just 1 |
.domain |
string |
The n9e site URL, used to build redirect links |
Automatically injected shorthands (no need to write by hand):
{{ $events := .events }}
{{ $event := index $events 0 }}
{{ $labels := $event.TagsMap }}
{{ $value := $event.TriggerValue }}
So inside the template you can directly use $event.xxx, $labels.agent_hostname, and $value.
Available $event Fields (*AlertCurEvent)
Common Fields
| field | type | description |
|---|---|---|
.Id |
int64 | Alert event ID (used to build the redirect link) |
.RuleId |
int64 | Alert rule ID |
.RuleName |
string | Rule name |
.RuleNote |
string | Rule note |
.Severity |
int | Alert severity: 1=Critical, 2=Warning, 3=Info |
.PromQl |
string | Alert trigger expression |
.RuleAlgo |
string | Rule algorithm type |
.TriggerTime |
int64 | Trigger time, unix seconds |
.TriggerValue |
string | Metric value at trigger time (already a string) |
.FirstTriggerTime |
int64 | First abnormal time (for consecutive alerts) |
.LastEvalTime |
int64 | Most recent evaluation time, used as the recovery time on recovery |
.IsRecovered |
bool | Whether it has recovered |
.NotifyCurNumber |
int | Which notification number this send is |
.TargetIdent |
string | Monitored object (usually agent_hostname) |
.TargetNote |
string | Object note |
.GroupId / .GroupName |
int64 / string | Business group |
.Cluster |
string | Data source cluster name |
.Cate |
string | Data source type (prometheus / host / mysql / ...) |
.RunbookUrl |
string | Runbook link |
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.
- 1mo ago First seen · 415 lines · 59 tokens per session scan A 386c9ab2610f
generate-message-template is a skill published in the GitHub repository ccfos/nightingale (13,395 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 5,258 once invoked, about $0.0002 per session on Opus 5.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-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.
k8s-monitoring-alerting
A Kubernetes diagnostic and repair method for Prometheus and Grafana monitoring problems, including alerts that do not trigger. Prometheus collects measurements, while Grafana displays them in dashboards.
datadog
Full-stack observability with Datadog APM, logs, metrics, synthetics, and RUM. Use when implementing monitoring, tracing, alerting, or cost optimization for production systems.
observability-testing-patterns
Observability and monitoring validation patterns for dashboards, alerting, log aggregation, APM traces, and SLA/SLO verification. Use when testing monitoring infrastructure, dashboard accuracy, alert rules, or metric pipelines.