assess-and-explain-threat

assess-and-explain-threat is a skill for Claude Code, Codex from gaelic-ghost/socket. It costs 44 tokens per session (416 once invoked), scanned A, original, Apache-2.0.

A workflow for deciding whether suspicious evidence represents a real threat and explaining the conclusion in plain language.

In plain words
What is it for?
Use it to weigh evidence, assess possible access or damage, state confidence and uncertainty, and recommend proportionate protective actions.
Why use it?
It separates direct observations from weak indicators, scanner results, and speculation, so people can act without overstating certainty.

Skill for Claude CodeCodex

Part of the cybersecurity-skills plugin — 31 skills shipped together

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.

agentmods
npx agentmods add skills/gaelic-ghost/socket/assess-and-explain-threat
Any agent
npx skills add gaelic-ghost/socket --skill assess-and-explain-threat
Clone the repo
git clone --depth 1 https://github.com/gaelic-ghost/socket

Made for: Claude Code, Codex.

Or install cybersecurity-skills, the plugin that ships this one along with the rest of its 31 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 assess-and-explain-threat

README.md
[![agentmods](https://agentmods.dev/badge/skills/gaelic-ghost/socket/assess-and-explain-threat.svg)](https://agentmods.dev/skills/gaelic-ghost/socket/assess-and-explain-threat)
Your own site
<a href="https://agentmods.dev/skills/gaelic-ghost/socket/assess-and-explain-threat"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/assess-and-explain-threat.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 416 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00044 $0.00416
Opus 5 $0.00022 $0.00208
Sonnet 5 $0.00009 $0.00083
Haiku 4.5 $0.00004 $0.00042

Measured 2d ago against content hash 607a16f26800, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

assess-and-explain-threat 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 2d 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/cybersecurity-skills/skills/assess-and-explain-threat/SKILL.md · 43 lines

What it actually says

Assess And Explain Threat

Overview

Turn mixed evidence into a proportionate conclusion and advice the affected person can follow. Do not collapse signatures, reputation, scanner output, or unusual behavior into a binary safe/malicious verdict.

Read references/confidence-and-advice.md for conclusion vocabulary and the explanation shape.

Workflow

  1. Restate the decision.

    • Identify what the user must decide now and what can wait for more evidence.
  2. Grade evidence by directness.

    • Separate direct observations, reproducible behaviors, vendor or threat-intelligence claims, weak indicators, absence of findings, and speculation.
    • Record contradicting evidence and coverage gaps.
  3. Assess behavior and impact.

    • State what access, execution, persistence, collection, credential use, network behavior, or data exposure is observed or technically plausible.
    • Distinguish capability from intent and artifact presence from successful compromise.
  4. Choose a calibrated classification.

    • Use one classification from the reference and state confidence separately.
    • Name the strongest supporting evidence and what would change the conclusion.
  5. Give proportionate advice.

    • Put urgent harm-reduction actions first.
    • Separate containment, evidence preservation, recovery, credential actions, notification, and long-term hardening.
    • Avoid destructive cleanup when evidence is weak and reversible isolation is available.
  6. Give a plain-language explanation.

    • Answer whether the concern is dangerous, what it appears to do, what is known versus inferred, what to do now, and when to escalate.
    • Define specialist terms at first use and avoid fear-amplifying language.

Output

Return the conclusion, confidence, decisive evidence, contradictions/gaps, immediate actions, follow-up analysis, and a short non-specialist explanation.

Files

What ships with it

2 files 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.

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. 2d ago First seen · 43 lines · 44 tokens per session scan A 607a16f26800

Subscribe to this mod's changes

assess-and-explain-threat is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 10d ago), licensed Apache-2.0. It adds 44 tokens to every session and 416 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

pipeline

Use when the user wants a feature idea taken end-to-end in one autonomous run — phrases like "run the whole pipeline", "take this feature from idea to finished branch", "brainstorm then build it autonomously", "do everything from idea to merged", "implement all phases without stopping". Triggers when they want…

kardebadas/claude-plugin · 80 tokens

craft

Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…

kardebadas/claude-plugin · 83 tokens

bug-fix

Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.

kardebadas/claude-plugin · 74 tokens

bug-investigate

Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …

kardebadas/claude-plugin · 83 tokens

setup

Use when superb's skills need their dependencies installed or checked — "set up superb", "install the dependencies", "why does pipeline say superpowers is missing", after a fresh plugin install, or on a new machine. Also use when a skill fails complaining that a superpowers sub-skill cannot be found.

kardebadas/claude-plugin · 64 tokens

chief-financial-officer

Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…

cbrock84/headcount · 88 tokens