analyze-incident

analyze-incident is a skill for Claude Code from bdmorin/the-no-shop. It costs 11 tokens per session (612 once invoked), scanned A, original, MIT.

A cybersecurity-incident analysis guide that extracts dates, attack methods, affected targets, attackers, and business impact from articles.

In plain words
What is it for?
Use it to summarize cyberattacks, identify exploited components and CVEs, and record affected organizations and consequences.
Why use it?
It organizes breach reports into the same concise fields, making different incidents easier to compare.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the fabric-analysis plugin — 34 skills shipped together

Good fit Use it to summarize cyberattacks, identify exploited components and CVEs, and record affected organizations and consequences.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bdmorin/the-no-shop/analyze-incident
Install

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.

Any agent
npx skills add bdmorin/the-no-shop --skill analyze-incident
Clone the repo
git clone --depth 1 https://github.com/bdmorin/the-no-shop

Made for: Claude Code.

Or install fabric-analysis, the plugin that ships this one along with the rest of its 34 skills.

Wrote 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.

agentmods badge for analyze-incident

README.md
[![agentmods](https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-incident/github.svg)](https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-incident)
Your own site
<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-incident"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-incident/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.

agentmods 80×15 button for analyze-incident

Your own site · 80×15
<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-incident"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.00612
Opus 5.5 $0.00004 $0.00245
Sonnet 5.5 $0.00002 $0.00122
Haiku 4.5 $0.00001 $0.00061

Measured 1mo ago against content hash 49d1e3bb6947, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyze-incident 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.

plugins/fabric-analysis/skills/analyze-incident/SKILL.md · 55 lines

What it actually says

Cybersecurity Hack Article Analysis: Efficient Data Extraction

Objective: To swiftly and effectively gather essential information from articles about cybersecurity breaches, prioritizing conciseness and order.

Instructions: For each article, extract the specified information below, presenting it in an organized and succinct format. Ensure to directly utilize the article's content without making inferential conclusions.

  • Attack Date: YYYY-MM-DD
  • Summary: A concise overview in one sentence.
  • Key Details:
    • Attack Type: Main method used (e.g., "Ransomware").
    • Vulnerable Component: The exploited element (e.g., "Email system").
    • Attacker Information:
      • Name/Organization: When available (e.g., "APT28").
      • Country of Origin: If identified (e.g., "China").
    • Target Information:
      • Name: The targeted entity.
      • Country: Location of impact (e.g., "USA").
      • Size: Entity size (e.g., "Large enterprise").
      • Industry: Affected sector (e.g., "Healthcare").
    • Incident Details:
      • CVE's: Identified CVEs (e.g., CVE-XXX, CVE-XXX).
      • Accounts Compromised: Quantity (e.g., "5000").
      • Business Impact: Brief description (e.g., "Operational disruption").
      • Impact Explanation: In one sentence.
      • Root Cause: Principal reason (e.g., "Unpatched software").
  • Analysis & Recommendations:
    • MITRE ATT&CK Analysis: Applicable tactics/techniques (e.g., "T1566, T1486").
    • Atomic Red Team Atomics: Recommended tests (e.g., "T1566.001").
    • Remediation:
      • Recommendation: Summary of action (e.g., "Implement MFA").
      • Action Plan: Stepwise approach (e.g., "1. Update software, 2. Train staff").
    • Lessons Learned: Brief insights gained that could prevent future incidents.

Attribution

Changes

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.

  1. 1mo ago First seen · 55 lines · 0 tokens per session scan A 49d1e3bb6947

Subscribe to this mod's changes

analyze-incident is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 612 once invoked, about $0.0000 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-31.

Related

Other skills, from other repositories

vast-ai-gpu-cloud

Safely inspect and operate Vast.ai marketplace instances with the vastai CLI, live offer data, and explicit approval before paid or destructive actions.

synthetic-sciences/openscience · 34 tokens

imaging-data-commons

Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Use for accessing large-scale radiology (CT, MR, PET) and pathology datasets for AI training or research. No authentication required. Query by metadata, visualize in browser, check licenses.

synthetic-sciences/openscience · 62 tokens

flow-cytometry-analysis

Complete flow cytometry analysis pipeline. FCS file handling, compensation, manual/automated gating, immunophenotyping, CFSE proliferation analysis, cell cycle analysis (Dean-Jett-Fox), and apoptosis assays. Extends flowio with analytical workflows. For raw FCS parsing only use flowio.

synthetic-sciences/openscience · 67 tokens

molecular-cloning

Molecular cloning simulation and design. PCR amplicon prediction, restriction enzyme digestion, Golden Gate and Gibson assembly simulation, primer design, CRISPR sgRNA design, and plasmid annotation. For protein-level sequence analysis use biopython or esm; for database lookups use gene-database or ensembl-database.

synthetic-sciences/openscience · 70 tokens

datamol

Pythonic wrapper around RDKit with simplified interface and sensible defaults. Preferred for standard drug discovery including SMILES parsing, standardization, descriptors, fingerprints, clustering, 3D conformers, parallel processing. Returns native rdkit.Chem.Mol objects. For advanced control or custom parameters…

synthetic-sciences/openscience · 67 tokens

shap

Model interpretability and explainability using SHAP (SHapley Additive exPlanations). Use this skill when explaining machine learning model predictions, computing feature importance, generating SHAP plots (waterfall, beeswarm, bar, scatter, force, heatmap), debugging models, analyzing model bias or fairness, comparing…

synthetic-sciences/openscience · 109 tokens