Is building-threat-hunt-hypothesis-framework safe to install?

SaferSkills independently audited building-threat-hunt-hypothesis-framework (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

cursor-claude-codex/skills/anthropic-cybersecurity-skills/skills/building-threat-hunt-hypothesis-framework/SKILL.md · 1 file

cursor-claude-codex/skills/anthropic-cybersecurity-skills/skills/building-threat-hunt-hypothesis-framework/SKILL.md3.2 KB · Markdown

name: building-threat-hunt-hypothesis-framework

description: Build a systematic threat hunt hypothesis framework that transforms threat intelligence, attack patterns, and

environmental data into testable hunting hypotheses.

domain: cybersecurity

subdomain: threat-hunting

tags:

- threat-hunting

- methodology

- hypothesis

- threat-intelligence

- hunting-framework

- proactive-detection

version: '1.0'

author: mahipal

license: Apache-2.0

nist_csf:

- DE.CM-01

- DE.AE-02

- DE.AE-07

- ID.RA-05

Building Threat Hunt Hypothesis Framework

When to Use

When proactively hunting for indicators of building threat hunt hypothesis framework in the environment
After threat intelligence indicates active campaigns using these techniques
During incident response to scope compromise related to these techniques
When EDR or SIEM alerts trigger on related indicators
During periodic security assessments and purple team exercises

Prerequisites

EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)
SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)
Sysmon deployed with comprehensive configuration
Windows Security Event Log forwarding enabled
Threat intelligence feeds for IOC correlation

Workflow

Formulate Hypothesis: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.
Identify Data Sources: Determine which logs and telemetry are needed to validate or refute the hypothesis.
Execute Queries: Run detection queries against SIEM and EDR platforms to collect relevant events.
Analyze Results: Examine query results for anomalies, correlating across multiple data sources.
Validate Findings: Distinguish true positives from false positives through contextual analysis.
Correlate Activity: Link findings to broader attack chains and threat actor TTPs.
Document and Report: Record findings, update detection rules, and recommend response actions.

Key Concepts

Concept	Description
TA0001	Initial Access
TA0003	Persistence
TA0008	Lateral Movement
TA0010	Exfiltration

Tools & Systems

Tool	Purpose
CrowdStrike Falcon	EDR telemetry and threat detection
Microsoft Defender for Endpoint	Advanced hunting with KQL
Splunk Enterprise	SIEM log analysis with SPL queries
Elastic Security	Detection rules and investigation timeline
Sysmon	Detailed Windows event monitoring
Velociraptor	Endpoint artifact collection and hunting
Sigma Rules	Cross-platform detection rule format

Common Scenarios

Scenario 1: Intelligence-driven hunt based on APT campaign report
Scenario 2: ATT&CK coverage gap analysis driving hypothesis creation
Scenario 3: Anomaly-driven hypothesis from UEBA alert investigation
Scenario 4: Situational awareness hunt based on industry sector threats

Output Format

Hunt ID: TH-BUILDI-[DATE]-[SEQ]
Technique: TA0001
Host: [Hostname]
User: [Account context]
Evidence: [Log entries, process trees, network data]
Risk Level: [Critical/High/Medium/Low]
Confidence: [High/Medium/Low]
Recommended Action: [Containment, investigation, monitoring]

building-threat-hunt-hypothesis-framework— agent skill

Is building-threat-hunt-hypothesis-framework safe to install?

Building Threat Hunt Hypothesis Framework

When to Use

Prerequisites

Workflow

Key Concepts

Tools & Systems

Common Scenarios

Output Format

Audit the pieces. Scan the whole. Decide.