CC reefwatch
Continuous local security monitoring daemon for Linux and macOS. Detects brute-force attacks, malware, privilege escalation, suspicious processes, file tampering, cryptominers, and network anomalies using YARA, Sigma, and custom detection rules. Runs as a background process and alerts only when real threats are found. Use when the user wants host-level intrusion detection, security monitoring, threat scanning, or asks about suspicious activity on their machine.
Continuous local security monitoring daemon for Linux and macOS.
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 19
✓ No critical or high findings
Medium and low: 19
-
medium Dangerous commands
cmd-persistenceREADME.md:85Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)cp service/com.reefwatch.daemon.plist ~/Library/LaunchAgents/
security skill -
medium Dangerous commands
cmd-persistenceREADME.md:86Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)launchctl load ~/Library/LaunchAgents/com.reefwatch.daemon.plist
security skill -
medium Dangerous commands
cmd-persistencereefwatch_config.yaml:58Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)- "/etc/crontab"
code literal -
medium Dangerous commands
cmd-persistencereefwatch_config.yaml:65Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)- "~/Library/LaunchAgents/"
code literal -
medium Dangerous commands
cmd-persistencereefwatch_config.yaml:66Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)- "/Library/LaunchDaemons/"
code literal -
medium Dangerous commands
cmd-persistencereefwatch/daemon.py:89Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)"/etc/crontab",
code literal -
low Risky intent
intent-offensive-securityREADME.md:14Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- **Malware** -- Known signatures via YARA (webshells, miners, ransomware, RATs)
detector -
low Risky intent
intent-offensive-securityREADME.md:15Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **Privilege escalation** -- SUID abuse, sudo exploits, unauthorized root access
-
low Secrets in code
secret-high-entropy-tokenreefwatch/engines/custom_rules.py:39High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"ZGlz…mcp",
quoted -
low Secrets in code
secret-high-entropy-tokenreefwatch/engines/custom_rules.py:40High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"bmV3…XB0",
quoted -
low Secrets in code
secret-high-entropy-tokenreefwatch/engines/custom_rules.py:43High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"c3Vi…W4p",
quoted -
low Secrets in code
secret-high-entropy-tokenreefwatch/engines/custom_rules.py:46High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"YWN0…W91",
quoted -
low Dangerous commands
cmd-eval-dynamicsetup_rules.py:384Dynamic code execution from decoded/untrusted input (quoted — discussed, not commanded)$py1 = "exec(compile(" asciiquoted -
low Dangerous commands
cmd-privilegesetup_rules.py:445Privilege escalation / world-writable permissions (string literal in code, not executed)$s5 = "chmod 777" ascii
code literal -
low Risky intent
intent-offensive-securitySKILL.md:4Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)description: "Continuous local security monitoring daemon for Linux and macOS. Detects brute-force attacks, malware, privilege escalation, suspicious processes, file tampering, cryptominers, and netwo
detector -
low Risky intent
intent-offensive-securitySKILL.md:26Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- **YARA**: File and process scanning for malware, webshells, miners, ransomware
detector -
low Risky intent
intent-offensive-securitySKILL.md:27Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- **Sigma**: Log-based detection for brute-force, privilege escalation, lateral movement
detector -
low Risky intent
intent-offensive-securitythreat_catalog.md:19Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Ransomware indicators | YARA | CRITICAL | Ransom note patterns, encryption behaviors |
-
low Risky intent
intent-offensive-securitythreat_catalog.md:22Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### Privilege Escalation
Files scanned: 26. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 940 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 465: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.