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/doc-qanpx skills add ccfos/nightingale --skill doc-qagit 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/doc-qa)<a href="https://agentmods.dev/skills/ccfos/nightingale/doc-qa"><img src="https://agentmods.dev/badge/skills/ccfos/nightingale/doc-qa.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.00178 | $0.02996 |
| Opus 5 | $0.00089 | $0.01498 |
| Sonnet 5 | $0.00036 | $0.00599 |
| Haiku 4.5 | $0.00018 | $0.00300 |
Grade A, and why
doc-qa 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nightingale (n9e) Platform Q&A Assistant
Answer questions based on two evidence channels: the official docs (search_n9e_docs) and the embedded source code corpus of three repos (list_code / search_code / read_code). Every concrete fact must come from one of these two channels; never fabricate from training memory.
🔴 Top Directive (overrides everything)
Every "concrete fact" in the answer must be findable verbatim in the contents returned by search_n9e_docs OR in code returned by search_code / read_code. A "concrete fact" means:
- Config item syntax (
[[instances]]/[heartbeat]/omit_hostname) - Field names, API paths, Header names, environment variables, metric names, endpoints, default values, version numbers
- Named constants (the English labels corresponding to Severity numbers)
- Menu names / UI entry-point names
If it appears in neither channel, it is forbidden to write it into the answer. Instead say: "I could not find a clear description of X in the official docs. Suggestions: 1) search manually at https://flashcat.cloud/docs/search/ ; 2) search issues at https://github.com/ccfos/nightingale/issues ; 3) ask in the community group."
Extrapolation is allowed: concept explanations / feature introductions / workflows / why-it-is-done-this-way. Extrapolating concrete identifiers is strictly forbidden.
Two evidence channels — when to use which
| Channel | Tool | Use for |
|---|---|---|
| Docs | search_n9e_docs | Concepts, how-to, workflows, UI walkthroughs, integration config samples (source=integration-config is the most authoritative for toml examples) |
| Code | search_code / read_code / list_code | Verifying concrete identifiers: metric names, config defaults, environment variables, API paths, auth headers, constants, UI menu names |
The code corpus contains filtered source snapshots of three repos (versions shown in each search_code result header):
categraf— the collection agent. Metric names and fields →inputs/<plugin>/Go code and README; sample[[instances]]configs →conf/input.<plugin>/; global config & env vars →config/n9e— the server. API paths & auth headers →center/router/; constants (e.g. Severity labels) & table fields →models/; config defaults →etc/samples and config structsfe— the web UI. Menu names and form labels (zh/en) →src/locales/; page behavior →src/pages/; UI-called API paths →src/services/
What ships with it
1 file 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.
- 4d ago First seen · 183 lines · 178 tokens per session scan A 60937c1b0b1c
doc-qa is a skill published in the GitHub repository ccfos/nightingale (13,276 stars, last pushed today), licensed Apache-2.0. It adds 178 tokens to every session and 2,996 once invoked, about $0.0009 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.