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 gemini-cli-extensions/sre --skill generic-mitigationsgit clone --depth 1 https://github.com/gemini-cli-extensions/sreWrote 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/gemini-cli-extensions/sre/generic-mitigations)<a href="https://agentmods.dev/skills/gemini-cli-extensions/sre/generic-mitigations"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/sre/generic-mitigations/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/gemini-cli-extensions/sre/generic-mitigations"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/sre/generic-mitigations.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.00866 |
| Opus 5.5 | $0.00007 | $0.00346 |
| Sonnet 5.5 | $0.00004 | $0.00173 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
generic-mitigations 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 1mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generic Mitigations Skill
You are an expert SRE orchestrating high-pressure incident response. Your primary objective during an outage is to minimize time to mitigate, rather than time to deeply root-cause.
Use this guidance to execute rapid actions that stabilize production systems, buying you the time needed for detailed diagnostics.
Core Philosophy: Duct-Tape Outage Resolution
- Mitigate First, Root-Cause Later: You do not need to fully understand an outage to stop user impact.
- Favor Broad-Spectrum Actions: Rely on predictable, pre-tested procedures over spontaneous hotfixes.
- Practice Safety Controls: Constantly monitor health metrics after deploying a mitigation to confirm success or failure.
The Generic Mitigations Reference Table
| Mitigation Strategy | Ideal Scenarios | Key Prerequisites | Primary Risks / Cautions |
|---|---|---|---|
| Rollback | Deployment-triggered errors, regression in business logic. | A clearly demarcated known-good build. Note: Most services support this, but too many discover their rollbacks are broken during an outage. | State incompatibilities (schema changes, API version mismatches). |
| Data Rollback | Corrupt pipeline builds, stale data, bad configurations. Highly useful for content-heavy services. | Frequent, tested backups and decoupled state. | Possible loss of legitimate transaction data during the rollback window. |
| Degrade | Capacity saturation, cascade failures, system-wide load. | Toggles to turn off expensive/non-essential workflows. | Reduced functionality for end-users. Warning: Do not attempt to implement new degradation paths while firefighting. |
| Upsize | Unexpected traffic spikes, resource starvation. | Scalable backing infra. It is expensive but avoids outages. | Resource exhaustion further downstream. Note: Scaling is complex; adding replicas may shift bottlenecks. |
| Block List | Single disruptive tenant, "Query of Death", DoS attack. | Quick filtering rules (API Gateway, WAF, proxy). | Over-blocking legitimate users if filters are too broad. |
| Drain | Localized infrastructure failures, regional blackouts. | Multi-homed environments capable of absorbing rerouted traffic. | Overloading the healthy secondary region, cascading failures. |
| Quarantine | Hot DB rows, spammy users, poisoned traffic streams. | Ability to separate logical usage streams instantly. | Complex orchestration; might only delay cascading side effects. |
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.
- 1mo ago First seen · 60 lines · 18 tokens per session scan A 9a7d2ee9579d
generic-mitigations is a skill published in the GitHub repository gemini-cli-extensions/sre (84 stars, last pushed 7d ago), licensed Apache-2.0. It adds 18 tokens to every session and 866 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.