Agent skill

Threat Detection

MITAuto-check: notesSecurity

Install Threat Detection

skills CLI

$ npx skills add borghei/Claude-Skills --skill threat-detection -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills threat-detection --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/threat-detection .claude/skills/threat-detection && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "threat-detection" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/threat-detection into .claude/skills/threat-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-detection", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/engineering/threat-detection

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add borghei/Claude-Skills --skill threat-detection -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills threat-detection --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/threat-detection .agents/skills/threat-detection && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "threat-detection" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/threat-detection into .agents/skills/threat-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-detection", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add borghei/Claude-Skills --skill threat-detection -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills threat-detection --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/threat-detection .cursor/skills/threat-detection && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "threat-detection" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/threat-detection into .cursor/skills/threat-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-detection", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/borghei/Claude-Skills.git --path engineering/threat-detection

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add borghei/Claude-Skills --skill threat-detection -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills threat-detection --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/threat-detection .gemini/skills/threat-detection && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "threat-detection" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/threat-detection into .gemini/skills/threat-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-detection", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install borghei/Claude-Skills threat-detection

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add borghei/Claude-Skills --skill threat-detection -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/threat-detection .github/skills/threat-detection && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "threat-detection" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/threat-detection into .github/skills/threat-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-detection", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add borghei/Claude-Skills --skill threat-detection -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills threat-detection --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/threat-detection .opencode/skills/threat-detection && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "threat-detection" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/threat-detection into .opencode/skills/threat-detection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "threat-detection", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: threat-detection
GitHub stars: 881
Token cost: ~1.3k tokens
SKILL.md length: 447 words
Files: 3 (incl. scripts, references)
Skills in repo: 349
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 5 steps: Collect - Gather logs from auth, access,… → Analyze - Run threat_signal_analyzer.py… → Triage - Review critical and high… → …
Asks to analyze logs for threats
SKILL.md covers Overview, Clarify First, Quick Start and Tools Overview, plus 3 more sections
Runs Python scripts from its folder; calls python

What it does

Threat Detection is an agent skill from borghei/Claude-Skills. This skill should be used when the user asks to "analyze logs for threats", "detect suspicious activity", "scan for brute force attempts", "identify injection attacks", or "audit access patterns for anomalies".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files (for example `references/threat-indicators.md` and `scripts/threat_signal_analyzer.py`).

It sits in Security. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

Asks to analyze logs for threats
Detect suspicious activity
Scan for brute force attempts
Identify injection attacks

Example prompts

“analyze logs for threats”
“detect suspicious activity”
“scan for brute force attempts”
“/threat-detection”

Requirements

Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Collect - Gather logs from auth, access, application sources
Analyze - Run threat_signal_analyzer.py across log files
Triage - Review critical and high severity findings first
Correlate - Cross-reference findings across log sources
Respond - Block IPs, reset credentials, escalate as needed

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Threat Detection loads about 1.3k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 447 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~57
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteRuns commands with sudoSKILL.md:62

| Privilege escalation | Detects sudo abuse, role changes, permission modifications |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 447 words, ~1,264 tokens.

Download SKILL.mdSave it as .claude/skills/threat-detection/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: threat-detection
description: This skill should be used when the user asks to "analyze logs for threats", "detect suspicious activity", "scan for brute force attempts", "identify injection attacks", or "audit access patterns for anomalies".
license: MIT + Commons Clause
metadata.version: 1.0.0
metadata.author: borghei
metadata.category: engineering
metadata.domain: security
metadata.updated: 2026-04-02
metadata.tags: security, threat-detection, logs, monitoring, incident-response

Threat Detection

Category: Engineering Domain: Security Operations

Overview

The Threat Detection skill provides automated analysis of log files for suspicious patterns including brute force attacks, injection attempts, unusual access patterns, and privilege escalation indicators. It helps security teams triage log data and identify threats before they escalate.

Clarify First

Before analyzing logs, confirm these inputs. If any is unknown or vague, ASK — do not assume:

Log file & source type — auth / access / application logs to analyze (--file; the subject of detection)
Threat category — brute force / injection / access anomaly / privilege escalation (--category; focuses the scan)
Minimum severity — the reporting/alert threshold (--min-severity; changes which signals surface and any SIEM/CI gate)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

bash

# Analyze a log file for threat signals
python scripts/threat_signal_analyzer.py --file /var/log/auth.log

# Analyze with specific threat category
python scripts/threat_signal_analyzer.py --file access.log --category injection

# JSON output for SIEM integration
python scripts/threat_signal_analyzer.py --file auth.log --format json

# Set minimum severity
python scripts/threat_signal_analyzer.py --file access.log --min-severity high

Tools Overview

threat_signal_analyzer.py

Analyzes log files for suspicious activity patterns across multiple threat categories.

Feature	Description
Brute force detection	Identifies repeated failed login attempts from same source
Injection scanning	Detects SQL injection, XSS, command injection in requests
Access anomalies	Flags unusual access times, forbidden paths, admin probes
Privilege escalation	Detects sudo abuse, role changes, permission modifications
Rate analysis	Identifies request flooding and denial-of-service patterns
IP reputation	Flags known-bad patterns (scanners, bots, TOR indicators)

Workflows

Log Analysis Workflow

Collect - Gather logs from auth, access, application sources
Analyze - Run threat_signal_analyzer.py across log files
Triage - Review critical and high severity findings first
Correlate - Cross-reference findings across log sources
Respond - Block IPs, reset credentials, escalate as needed

Show full SKILL.md (191 more words)Show less

Incident Investigation Workflow

Scope - Identify time window and affected systems
Scan - Run analyzer on all relevant log files
Timeline - Build timeline from threat signals
Impact - Assess what was accessed or modified
Contain - Block threat actors and patch vulnerabilities

Continuous Monitoring

bash

# Cron job: analyze auth logs every hour
python scripts/threat_signal_analyzer.py --file /var/log/auth.log --format json --min-severity high > /tmp/threat_report.json

# CI/CD: scan application logs on deployment
python scripts/threat_signal_analyzer.py --file app.log --category injection --format json

Reference Documentation

Threat Indicators - Common attack patterns, indicators of compromise, response playbooks

Common Patterns Quick Reference

Threat Categories

Category	Signals	Severity
Brute force	5+ failed logins from same IP in 5 min	High
SQL injection	UNION SELECT, OR 1=1, DROP TABLE in requests	Critical
XSS	script tags, javascript: URIs, event handlers in input	High
Path traversal	../ sequences, /etc/passwd access attempts	High
Command injection	; cat /etc/passwd,	nc, backtick usage
Admin probing	/admin, /wp-admin, /phpmyadmin access attempts	Medium
Rate flooding	100+ requests/minute from single IP	High

Severity Levels

CRITICAL - Active exploitation attempt (injection, RCE)
HIGH - Likely attack in progress (brute force, privilege escalation)
MEDIUM - Suspicious activity requiring investigation
LOW - Informational, possible false positive

Response Actions

Severity	Immediate Action	Follow-Up
Critical	Block IP, alert SOC	Incident report, forensics
High	Rate limit, monitor	Review access, check damage
Medium	Log and monitor	Weekly review
Low	Log only	Monthly trend analysis

Files

SKILL.md and 2 other files (scripts, references) in engineering/threat-detection of borghei/Claude-Skills.

SKILL.md
references/threat-indicators.md
scripts/threat_signal_analyzer.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Threat Detection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Threat Detection compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Threat Detection this skillborghei/Claude-Skills	881	—	~1.3k	Automated safety check: Notes	MIT	yesterday
Fla Ascend Performancefla-org/flash-linear-attention	5.8k	—	~6.3k	Automated safety check: Pass	MIT	today
Deepsec Documentation Guidevercel-labs/deepsec	8.1k	—	~956	Automated safety check: Pass	Apache-2.0	9 days ago
Skill Scannergetsentry/skills	1k	4 repos	~2.5k	Automated safety check: Warn	Apache-2.0	5 days ago
Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit	480	1 repos	~3.3k	Automated safety check: Pass	None	7 days ago
Security Alert Triageelastic/agent-skills	592	1 repos	~3.5k	Automated safety check: Notes	Apache-2.0	yesterday

Similar skills

Fla Ascend Performance
fla-org/flash-linear-attention
Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.
5.8k GitHub stars~6.3k tokensUpdated today
SecurityAuto-check passed
Deepsec Documentation Guide
vercel-labs/deepsec
Official
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
8.1k GitHub stars~956 tokensUpdated 9 days ago
SecurityAuto-check passed
Skill Scanner
getsentry/skills
Official
Scan agent skills for security issues. An agent skill from getsentry/skills.
1k GitHub starsUsed in 4 repos~2.5k tokens
SecurityAuto-check: warnings
Serenity Aleabitoreddit
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
480 GitHub starsUsed in 1 repo~3.3k tokens
SecurityAuto-check passed
Security Alert Triage
elastic/agent-skills
Official
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
592 GitHub starsUsed in 1 repo~3.5k tokens
SecurityAuto-check: notes
Shiro Attack CLI
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
2.6k GitHub stars~945 tokensUpdated 4 mo ago
SecurityAuto-check passed

Questions about Threat Detection

What does Threat Detection do?

This skill should be used when the user asks to "analyze logs for threats", "detect suspicious activity", "scan for brute force attempts", "identify injection attacks", or "audit access patterns for…. Threat Detection is an agent skill from borghei/Claude-Skills. This skill should be used when the user asks to "analyze logs for threats", "detect suspicious activity", "scan for brute force attempts", "identify injection attacks", or "audit access patterns for anomalies".

When should I use Threat Detection?

Threat Detection fits situations like: asks to analyze logs for threats; detect suspicious activity; scan for brute force attempts; identify injection attacks.

How do I install Threat Detection in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill threat-detection -a claude-code`. Or copy the skill folder (engineering/threat-detection in borghei/Claude-Skills) into .claude/skills/threat-detection in your project. Claude Code loads it when a task matches its description.

How do I install Threat Detection in Codex?

Run `npx skills add borghei/Claude-Skills --skill threat-detection -a codex`. Or copy the skill folder (engineering/threat-detection in borghei/Claude-Skills) into .agents/skills/threat-detection in your project. Codex loads it when a task matches its description.

Can I use Threat Detection in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill threat-detection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/threat-detection, .gemini/skills/threat-detection, .github/skills/threat-detection and .opencode/skills/threat-detection in your project.

What does Threat Detection need to run?

Going by SKILL.md and its folder, Threat Detection needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Threat Detection access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Threat Detection safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Threat Detection use?

Threat Detection is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Threat Detection use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.

What are the alternatives to Threat Detection?

Skills that share tags, products or a category with Threat Detection: Fla Ascend Performance (fla-org/flash-linear-attention, 5.8k stars), Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars) and Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 480 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Threat Detection?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Threat Detection

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Threat Detection

Overview

Clarify First

Quick Start

Tools Overview

threat_signal_analyzer.py

Workflows

Log Analysis Workflow

Incident Investigation Workflow

Continuous Monitoring

Reference Documentation

Common Patterns Quick Reference

Threat Categories

Severity Levels

Response Actions

Files

Compare with similar skills

Similar skills

More from borghei/Claude-Skills

Related

Questions about Threat Detection