borghei/threat-detection
> 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".
npx skills add https://github.com/borghei/Claude-Skills --skill threat-detection
> Category: Engineering
> Domain: Security Operations
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.
Before analyzing logs, confirm these inputs. If any is unknown or vague, ASK — do not assume:
--file; the subject of detection)--category; focuses the scan)--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.
# 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
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) |
# 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
| 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 | 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 |
Take borghei/threat-detection from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.