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/modify-dashboardnpx skills add ccfos/nightingale --skill modify-dashboardgit 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/modify-dashboard)<a href="https://agentmods.dev/skills/ccfos/nightingale/modify-dashboard"><img src="https://agentmods.dev/badge/skills/ccfos/nightingale/modify-dashboard.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 | $0.00089 | $0.02220 |
| Opus 5 | $0.00044 | $0.01110 |
| Sonnet 5 | $0.00018 | $0.00444 |
| Haiku 4.5 | $0.00009 | $0.00222 |
Grade A, and why
modify-dashboard 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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Nightingale (N9E) Modify an Existing Dashboard
Help users modify an existing dashboard using natural language — not create a new one. Three typical kinds of requests:
| Request | What you change |
|---|---|
| Change variables | A template variable's value expression (definition), default value, whether it is multi-select (multi), display label (label) |
| Check and fix variables | Scan variable definitions and the references to variables inside charts, detect smells (a chart references an undefined variable, a variable returns no value, datasource references are inconsistent, etc.) and fix them |
| Change chart series | The series of a chart (panel): query expression (PromQL), legend, unit, adding/removing series, changing the title, changing the chart type (e.g., stat→timeseries) |
Editing series queries (
queries) is only supported for Prometheus/VictoriaMetrics panels; SQL/log panels (mysql, ck, es, etc.) can only have their unit, title, description changed or be deleted — passingquerieswill be rejected by the tool.
Iron rule: a single proposal call wraps it up; confirmation is done by the system
update_dashboard is a proposal-style write: after you call it (passing only the part you want to change), the tool computes the diff, directly shows the user the list of changes and pauses the conversation; once the user confirms, the system automatically persists it to the database — the confirmation step neither needs nor goes through you. Therefore:
- First call
get_dashboard_detail(id, include_config=true)to read the current variables, chart summaries, and variable health check. - After working out the part you want to change, call
update_dashboardonce, passing only thevariables/panels/fix_datasourceyou want to change. This call is the last step of this turn; the system takes over the display and confirmation. - Do not render the change table yourself (the system will show the list generated by the tool), and do not pass
proposal_id/confirmed(those are parameters for the system's confirmation channel). - When the user rejects or raises a new requirement, you will receive feedback in a new turn: just recompute the changes per the feedback and call
update_dashboardagain (the old proposal is automatically voided).
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.
- 4d ago First seen · 104 lines · 89 tokens per session scan A 2f48368be49a
modify-dashboard is a skill published in the GitHub repository ccfos/nightingale (13,276 stars, last pushed yesterday), licensed Apache-2.0. It adds 89 tokens to every session and 2,220 once invoked, about $0.0004 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.
frontend-dashboard
Use this skill when editing the embedded dashboard frontend in this repository. It focuses on preserving the single-file embedded SPA model, keeping the UI lightweight, and avoiding unnecessary frontend tooling or dependencies.
embedded-captions
Add captions to a talking-head video. ONE catalog (CATALOG.md) of 32 visual identities behind two engines: column-flow (captions composited INTO the scene — matte occlusion + mix-blend; cream/ink/editorial/keynote/documentary/loud/neon/glitch/chrome/velocity) and themed constitutions…
atai-operational-state-monitoring-agent
Run Archetype AI's managed Operational State Monitoring (OSM) agent over the Agents API — upload a sensor CSV, resolve a maintained pre-packaged "OSM Quick Start" bundle (classifier + windowing already pinned), run it, poll status + audit events, download the per-window state predictions. Use when the user wants…
atai-rare-event-detection-agent
Run Archetype AI's managed Rare Event Detection (RED) agent over the Agents API — upload a sensor CSV, resolve the pre-packaged "RED Quick Start" bundle by name (its nearest-prototype classifier and windowing are already pinned), run it, poll status + audit events, download per-window event predictions. Use when the…
Alerting & Monitoring Testing
Testing monitoring and alerting configurations including threshold validation, alert routing, escalation policies, and false-positive rate monitoring.