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.
npx agentmods add skills/woohyun212/security-skill/log-analysisnpx skills add woohyun212/security-skill --skill log-analysisgit clone --depth 1 https://github.com/woohyun212/security-skillWrote 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.
[](https://agentmods.dev/skills/woohyun212/security-skill/log-analysis)<a href="https://agentmods.dev/skills/woohyun212/security-skill/log-analysis"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/log-analysis.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00018 | $0.02874 |
| Opus 5 | $0.00009 | $0.01437 |
| Sonnet 5 | $0.00004 | $0.00575 |
| Haiku 4.5 | $0.00002 | $0.00287 |
Grade A, and why
log-analysis scanned grade A with 1 finding 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 5d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| python3 not installed | Missing Python | `sudo apt install python3` | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this skill does
Analyzes security log files to detect anomalies. Extracts top IPs, paths, status codes, and User-Agents from web access logs, and detects brute-force patterns (multiple 401s) and scanning behavior (sequential path enumeration). Extracts failed login patterns from auth logs and error/warning patterns from syslog, then outputs a summary report with a timeline.
When to use
- Analyzing access logs when a web server compromise is suspected
- Checking whether an SSH brute-force attack has occurred
- Reconstructing an attack timeline during incident response
- Automating routine security monitoring and anomaly detection
Prerequisites
grep,awk,sort,uniq(available by default on most Linux systems)python3(advanced analysis and report generation)- Read access to the target log files
Inputs
| Field | Description | Example |
|---|---|---|
LOG_FILE |
Path to the log file to analyze | /var/log/nginx/access.log |
LOG_TYPE |
Log type: access / auth / syslog |
access |
TOP_N |
Number of top entries to display (default: 20) | 20 |
Workflow
Step 1: Verify log file and type
LOG_FILE="${SECSKILL_LOG_FILE:-${1:-}}"
LOG_TYPE="${SECSKILL_LOG_TYPE:-${2:-auto}}"
TOP_N="${SECSKILL_TOP_N:-${3:-20}}"
if [ -z "$LOG_FILE" ]; then
read -rp "Enter log file path: " LOG_FILE
fi
if [ ! -f "$LOG_FILE" ]; then
echo "[!] File not found: $LOG_FILE"
exit 1
fi
# Auto-detect log type
if [ "$LOG_TYPE" = "auto" ]; then
filename=$(basename "$LOG_FILE")
case "$filename" in
access*|nginx*|apache*|httpd*) LOG_TYPE="access" ;;
auth*|secure*|sshd*) LOG_TYPE="auth" ;;
syslog*|messages*|system*) LOG_TYPE="syslog" ;;
*) LOG_TYPE="access" ; echo "[*] Could not auto-detect log type, assuming access log." ;;
esac
fi
TOTAL_LINES=$(wc -l < "$LOG_FILE")
FILE_SIZE=$(du -sh "$LOG_FILE" | cut -f1)
echo "[+] Log file: $LOG_FILE"
echo " Type: $LOG_TYPE | Lines: $TOTAL_LINES | Size: $FILE_SIZE"
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.
- 5d ago First seen · 294 lines · 18 tokens per session scan A 0ed47e5ca223
log-analysis is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 2,874 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…