incident-response — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited incident-response (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
In an incident the priority order is: restore service → understand cause → prevent recurrence. Don't invert it by debugging a live outage while users suffer.
feature flag off, fail over, scale up, or shed load. The fastest safe path to "users are OK again" beats the elegant fix.
the real cause without the clock running.
change right before the incident is the prime suspect). Form one hypothesis at a time (see systematic-debugging).
time. Silence is worse than bad news.
action items to prevent recurrence (better alerting, a guard, a test). Focus on the system and process, not who.
Red flag: forward-fixing a live outage instead of rolling back; declaring it resolved without confirming recovery in the metrics.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.