Borrowing it
Nothing to install: this file belongs to dfirtnt/Huntable-CTI-Studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dfirtnt/Huntable-CTI-Studio/main/.claude/skills/add-source/SKILL.mdgit clone --depth 1 https://github.com/dfirtnt/Huntable-CTI-StudioWrote 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/dfirtnt/huntable-cti-studio/add-source)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/add-source"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/add-source/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/add-source"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/add-source.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00069 | $0.01370 |
| Opus 5 | $0.00034 | $0.00685 |
| Sonnet 5 | $0.00014 | $0.00274 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
add-source 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8001/api/health/ingestion | jq '.ingestion.source_breakdown[] | select(.source_name == "{Source Name}") | {name: .source_name, total: .articles_count}' How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Source
This skill adds a new CTI intelligence source to config/sources.yaml and syncs
it to the database. It handles both RSS-based and scraping-only sources.
Workflow
Step 1 — Gather source information
Collect from the user (ask if not provided):
| Field | Required | Example |
|---|---|---|
| Blog/site URL | Yes | https://www.vmray.com/blog/ |
| RSS feed URL | No | https://www.vmray.com/blog/feed/ |
| Source name | Yes (can derive) | VMRay Blog |
Step 2 — Discover source details
Use web tools to visit the site and determine:
- RSS feed discovery — Check for
<link rel="alternate" type="application/rss+xml">in the page head, or try common paths (/feed/,/rss/,/feed.xml,/rss.xml,/atom.xml). If an RSS URL was provided, validate it returns valid XML. - Domain — Extract the domain for the
allowlist (e.g.,vmray.com) - Post URL pattern — Look at article links to derive a
post_url_regex(e.g.,^https://www\\.vmray\\.com/blog/.*) - Content selectors — Inspect an article page for appropriate
body_selectors,title_selectors,date_selectors,author_selectorsif the site needs scraping - Content type — Determine if articles are CTI-relevant (threat intel, malware analysis, detection engineering, vulnerability research)
Step 3 — Generate the source identifier
Create a snake_case id from the source name:
VMRay Blog→vmray_blogUnit 42 Threat Research→unit42_threat_research
Check config/sources.yaml for duplicate identifiers before proceeding.
Step 4 — Build the YAML entry
Use this template, adapting based on discovery:
# {Source Name} — {brief note about RSS availability}
- id: "{identifier}"
name: "{Source Name}"
url: "{site_url}"
rss_url: {rss_url or null}
check_frequency: 14400 # 4 hours (system default; reduce to 1800 only after successful validation)
active: false # Start disabled; enable manually after verifying articles are ingested correctly
config:
allow: ["{domain}"]
post_url_regex: ["{regex_pattern}"]
robots:
enabled: true
user_agent: "Huntable-CTI-Studio/1.0 (+https://github.com/dfirtnt/Huntable-CTI-Studio)"
respect_delay: true
max_requests_per_minute: 10
crawl_delay: 1.0
min_content_length: 1500
title_filter_keywords: ["webinar", "training", "careers", "job posting"]
rss_only: {true if rss_url and no scraping needed, else false}
extract:
prefer_jsonld: true
title_selectors: ["h1", "meta[property='og:title']::attr(content)"]
date_selectors:
- "meta[property='article:published_time']::attr(content)"
- "time[datetime]::attr(datetime)"
body_selectors: {discovered selectors or defaults}
author_selectors: ["meta[name='author']::attr(content)", ".author-name"]
description: "{one-line description of what intelligence this source provides}"
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.
- 10d ago First seen · 125 lines · 69 tokens per session scan A 0ccbf7c6ae56
add-source is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 1,370 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
configuring-windows-event-logging-for-detection
Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and object access to feed SIEM detection rules. Activates for requests involving…
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
analyzing-ransomware-encryption-mechanisms
Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts. Covers AES, RSA, ChaCha20, and hybrid encryption schemes. Activates for requests involving ransomware…
analyzing-slack-space-and-file-system-artifacts
Examine file system slack space, MFT entries, USN journal, and alternate data streams to recover hidden data and reconstruct file activity on NTFS volumes.
conducting-external-reconnaissance-with-osint
Conducts external reconnaissance using Open Source Intelligence (OSINT) techniques to map an organization's external attack surface without directly interacting with target systems. The tester gathers information from public sources including DNS records, certificate transparency logs, search engines, social media…
conducting-mobile-app-penetration-test
Conducts penetration testing of iOS and Android mobile applications following the OWASP Mobile Application Security Testing Guide (MASTG) to identify vulnerabilities in data storage, network communication, authentication, cryptography, and platform-specific security controls. The tester performs static analysis of…