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 Arvo-AI/aurora --skill incidentiogit clone --depth 1 https://github.com/Arvo-AI/auroraWrote 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/arvo-ai/aurora/incidentio)<a href="https://agentmods.dev/skills/arvo-ai/aurora/incidentio"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/incidentio/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/arvo-ai/aurora/incidentio"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/incidentio.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.00018 | $0.00628 |
| Opus 5 | $0.00009 | $0.00314 |
| Sonnet 5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
incidentio 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 9d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
incident.io Integration
Overview
incident.io integration for investigating incidents during Root Cause Analysis. Provides access to incident details, severity, roles, custom fields, and timeline events.
Instructions
Tool Usage (use in this order)
list_incidentio_incidents()-- Find recent or related incidents. Filter by status or severity.get_incidentio_incident(incident_id='X')-- Get full details including roles, custom fields, and duration.get_incidentio_timeline(incident_id='X')-- See the sequence of events, status changes, and human updates.
Investigation Patterns
- Find similar incidents:
list_incidentio_incidents(status='closed', page_size=10)to check for recurring issues. - Deep-dive current incident:
get_incidentio_incident(incident_id='...')for severity, responders, and custom fields. - Understand timeline:
get_incidentio_timeline(incident_id='...')to see what actions were taken and when.
RCA Investigation Workflow
Step 1 -- Context gathering:
list_incidentio_incidents(status='live') -- See what's currently happening.
Step 2 -- Incident details:
get_incidentio_incident(incident_id='...') -- Understand severity, who's responding, and what services are affected.
Step 3 -- Timeline analysis:
get_incidentio_timeline(incident_id='...') -- Reconstruct the sequence of events to find the trigger point.
Step 4 -- Pattern matching:
list_incidentio_incidents(status='closed', page_size=25) -- Check if similar incidents happened before.
Step 5 -- Cross-correlate: After incident.io analysis, correlate with infrastructure data from other connected tools (logs, metrics, deployments).
Important Rules
- incident.io is a REMOTE service. Use only the API tools listed above.
- Start with
list_incidentio_incidentsto understand the landscape before diving into specifics. - Timeline data is essential for understanding causality -- always check it during RCA.
- Incident.io roles tell you who was involved, which helps validate findings.
- Custom fields often contain service/component info useful for correlation.
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.
- 9d ago First seen · 62 lines · 18 tokens per session scan A 3125d9e9d647
incidentio is a skill published in the GitHub repository Arvo-AI/aurora (406 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 628 once invoked, about $0.0001 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
tax-lawyer-software-interfaces
MCP tool design patterns for the Tax-Lawyer Platform. Thin Satisfies wrappers (<=10 lines per handler), TaxArgs contract types, and the full tool name taxonomy for ledgerrtax MCP actions.
b00t
Identify integration points, data flow via redis, suggest how to bridge VSCode plugin to b00t jobs, and outline k0s/podman/docker-agnostic redis interface. Include how ralph should be wrapped as b00t job with redis exchange + Azure access, and call out where integration tests are required. ONLY do this analysis. Reply…
terraform-infrastructure-as-code
Comprehensive Terraform Infrastructure as Code skill covering resources, modules, state management, workspaces, providers, and advanced patterns for cloud-agnostic infrastructure deployment.
isaac-automator
Deploy and operate a cloud Isaac Workstation with Isaac Automator: provision a GPU VM running Isaac Sim, Isaac Lab, and/or Isaac Lab Arena on AWS, GCP, Azure, or Alibaba Cloud, connect to it, move data in and out, control cost with stop/start, repair, import existing deployments, and destroy. Use when the user wants a…
cloud-iam-deep
GCP/AWS/Azure cloud exploitation -- Cloud Functions, Firestore, Cloud Run, S3, MinIO, Blob Storage, SA keys.
ak-add-integration
Add a messaging platform integration to an existing Agent Kernel project. This skill guides you through adding Slack, WhatsApp, Messenger, Instagram, Telegram, Teams, or Gmail integration by generating configuration, updating dependencies, and setting up webhook handlers. Designed for users extending their agents.