SkillAgentSearch skills...

threat-detection

Scan auth and access logs for brute force, injection, path traversal, admin probing and request floods, with triage guidance

Install / Use

npx skills add borghei/Claude-Skills --skill threat-detection

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Security

Supported Platforms

Universal

Our assessment of threat-detection

threat-detection scores 86/100 on our quality scale, 765th of 1,096 Security skills we index.

Its SKILL.md is 4.9 KB long, well organised into 21 sections with 2 code examples: a solid amount of guidance for an agent.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so threat-detection is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

threat-detection compared with similar skills

All 4 of these similar skills score higher than threat-detection; compare them before choosing.

SkillScoreStarsUpdatedFormat
threat-detection (this skill)by borghei8681757d agoSKILL.md
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md
prospectingby coreyhaines3110060.1k6d agoSKILL.md

Frequently asked questions

How do I install threat-detection?
Run npx skills add borghei/Claude-Skills --skill threat-detection. The install tabs above show the steps for each supported agent.
Which AI agents does threat-detection work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is threat-detection safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is threat-detection still maintained?
The repository was last updated about 2 months ago, so threat-detection is actively maintained.

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 author: borghei category: engineering domain: security updated: 2026-04-02 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

# 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

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

Incident Investigation Workflow

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

Continuous Monitoring

# 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 | Critical | | 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 |

Related Skills

View on GitHub
GitHub Stars817
CategorySecurity
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
threat-detection — Universal Skill: Install & Safety Check | SkillAgent