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 agentmods add skills/ccfos/nightingale/alert-subscribe-copilotnpx skills add ccfos/nightingale --skill alert-subscribe-copilotgit 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/alert-subscribe-copilot)<a href="https://agentmods.dev/skills/ccfos/nightingale/alert-subscribe-copilot"><img src="https://agentmods.dev/badge/skills/ccfos/nightingale/alert-subscribe-copilot.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.00137 | $0.02126 |
| Opus 5 | $0.00068 | $0.01063 |
| Sonnet 5 | $0.00027 | $0.00425 |
| Haiku 4.5 | $0.00014 | $0.00213 |
Grade A, and why
alert-subscribe-copilot 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 6d 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.
| `http-api.md` | HTTP API paths (for A2A / external agents), tryrun validation endpoint | Only for external A2A scenarios or when providing the user with curl commands | How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nightingale (n9e) Alert Subscription Rule Copilot
A subscription rule filters alert events by condition, clones a copy, and forwards it to the associated notification rule. Typical scenarios: cross-team CC, alert escalation (notify a supervisor only after N minutes of persistence), and aggregating events from scattered rules into a single outlet.
Supporting materials (load on demand with read_file, set base to this skill name)
| File | Content | When to read |
|---|---|---|
reference.md |
Full config field table, new vs. old notification version differences, redefine fields, complete examples | When you're unsure about a field while assembling config |
troubleshooting.md |
Subscription-not-taking-effect troubleshooting chain (in engine matching order), behavioral semantics, gotcha table | When the user says "I subscribed but didn't receive anything" |
http-api.md |
HTTP API paths (for A2A / external agents), tryrun validation endpoint | Only for external A2A scenarios or when providing the user with curl commands |
Prerequisites
You are the in-app AI assistant for n9e, running inside the n9e process and already authenticated as the current user. Operate directly via the built-in tools — do not log in, do not call HTTP APIs, and do not use http_fetch against your own endpoints (the HTTP flow in http-api.md is for external A2A agents).
Mental model
- Subscription happens at the notification stage (
alert/dispatch/dispatch.go:handleSubs): the original event still travels its own notification path as usual; each matching subscription clones a copy of the event, rewrites it per the subscription config, and then runs it through the notification chain again. A subscription is additive — it does not intercept and does not replace the original notification. - Match conditions are AND'd together and checked in order: enabled → datasource → prod → cate → tags → business group name → duration → severity. Failing any single gate skips that subscription.
- A subscription's
group_idis the management ownership (permissions) and does not participate in event matching — a subscription inherently receives events across business groups; to "subscribe only to a certain business group's events", use thebusi_groupsfilter condition. - New routing (
notify_version=1): the cloned event's notification outlet is rewritten to the subscription's specifiednotify_rule_ids; the cloned event's callbacks are cleared by default, to prevent re-hitting the original rule's callbacks. - Changes take effect within 9 seconds at most (the in-memory cache polling cycle).
What ships with it
3 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.
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.
- 6d ago First seen · 93 lines · 137 tokens per session scan A be85eebc4ff7
alert-subscribe-copilot is a skill published in the GitHub repository ccfos/nightingale (13,280 stars, last pushed 2d ago), licensed Apache-2.0. It adds 137 tokens to every session and 2,126 once invoked, about $0.0007 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
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.