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 spyrae/kronos-agent-os --skill incident-reviewgit clone --depth 1 https://github.com/spyrae/kronos-agent-osWrote 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/spyrae/kronos-agent-os/incident-review)<a href="https://agentmods.dev/skills/spyrae/kronos-agent-os/incident-review"><img src="https://agentmods.dev/badge/skills/spyrae/kronos-agent-os/incident-review/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/spyrae/kronos-agent-os/incident-review"><img src="https://agentmods.dev/badge/skills/spyrae/kronos-agent-os/incident-review.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.00021 | $0.00107 |
| Opus 5.5 | $0.00008 | $0.00043 |
| Sonnet 5.5 | $0.00004 | $0.00021 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
incident-review 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 2mo 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.
What it actually says
Incident Review
Protocol
- Build a timeline from the provided evidence.
- Separate facts from hypotheses.
- Identify impact, likely cause, and detection gaps.
- Recommend follow-up tasks and tests.
Safety
Do not restart services, mutate infrastructure, or run server ops unless the operator explicitly enabled the required capability gate.
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.
- 2mo ago First seen · 21 lines · 21 tokens per session scan A 18f90d6c7ffb
incident-review is a skill published in the GitHub repository spyrae/kronos-agent-os (65 stars, last pushed 9d ago), licensed MIT. It adds 21 tokens to every session and 107 once invoked, about $0.0001 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
remember
Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture…
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
python-lib-analyzer
Analyze any Python library structure, explore modules, classes, and functions with signatures and documentation.
rag-techniques-contribution-guidelines
Checks a RAGTechniques pull request against the repository's contribution guidelines (CONTRIBUTING.md): where new technique notebooks go, the README list entry and table row every new technique needs, the required notebook structure, and notebook hygiene. Use on any PR that adds or changes a notebook under…
q-review
Have each agent independently review real code changes (a branch, an open PR, a commit range, or the whole codebase), then converge over multiple rounds into a single findings table. Use when you want critical pushback on committed-but-unmerged work before it lands. Pass the target spec as the argument; add --scope…
q-validate
Have each agent independently review a plan file, then deliberate over additional rounds. Use when you have a draft plan and want critical pushback before committing. Pass the path to the plan file as the argument; add --verbose to lift terse output caps.