CB monitoring-darkweb-sources
Monitors dark web forums, marketplaces, paste sites, and ransomware leak sites for mentions of organizational assets, leaked credentials, threatened attacks, and threat actor communications to provide early warning intelligence. Use when establishing dark web monitoring coverage, investigating specific data breach claims, or enriching incident investigations with dark web context. Activates for requests involving dark web OSINT, leak site monitoring, credential exposure, Recorded Future dark web, or Tor hidden service intelligence.
Monitors dark web forums, marketplaces, paste sites, and ransomware leak sites for mentions of organizational assets, leaked credentials, threatened attacks…
As a process B 67/100 · Nearly there — weak spots: result and completion, failures and branches
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 · 10
✓ No critical or high findings
Medium and low: 10
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:19Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## Ransomware.live API
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:23Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| `/recentvictims` | GET | List recent ransomware leak site victims |
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:24Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| `/groups` | GET | List tracked ransomware groups |
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:25Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| `/group/{name}` | GET | Get details for a specific ransomware group | -
low Risky intent
intent-offensive-securityreferences/api-reference.md:36Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **requests**: HTTP client for HIBP, Dehashed, and ransomware.live APIs
-
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)description: 'Monitors dark web forums, marketplaces, paste sites, and ransomware
detector -
low Risky intent
intent-offensive-securitySKILL.md:18Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- ransomware-leaks
-
low Risky intent
intent-offensive-securitySKILL.md:78Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Investigating a reported data breach claim found on a ransomware leak site or paste site
-
low Risky intent
intent-offensive-securitySKILL.md:121Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### Step 3: Investigate Ransomware Leak Sites
-
low Risky intent
intent-offensive-securitySKILL.md:123Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Ransomware groups maintain .onion leak sites. Monitor these through commercial services rather than direct access. When a claim appears about your organization:
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "nist_ai_rmf" - note
frontmatter-keyunknown frontmatter key "atlas_techniques" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack" - note
frontmatter-keyunknown frontmatter key "mitre_f3"
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1638 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 537: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.