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/Create-Huntable-Agent/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/create-huntable-agent)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/create-huntable-agent"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/create-huntable-agent/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/create-huntable-agent"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/create-huntable-agent.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.00129 | $0.06391 |
| Opus 5 | $0.00064 | $0.03195 |
| Sonnet 5 | $0.00026 | $0.01278 |
| Haiku 4.5 | $0.00013 | $0.00639 |
Grade A, and why
create-huntable-agent scanned grade A with 0 findings 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 13d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Huntable Agent
This skill guides you through adding a new extraction sub-agent to Huntable CTI Studio's agentic workflow. The system uses a LangGraph-based pipeline with 7 steps, where Step 3 (ExtractAgent) is a supervisor that delegates to sub-agents. Each sub-agent has an optional QA agent for validation.
Before You Start
Read these files in order to understand the current codebase contract:
AGENTS.md— authoritative repo contractsrc/config/workflow_config_schema.py— Pydantic v2 schema (source of truth)src/config/workflow_config_loader.py— config load/export/importsrc/config/workflow_config_migrate.py— v1→v2 migration
Naming Convention
Every new agent needs three identifiers that must be consistent everywhere:
| Identifier | Example (Registry) | Pattern |
|---|---|---|
| AgentName (PascalCase) | RegistryExtract |
{Name}Extract |
| QAName (PascalCase) | RegistryQA |
{Name}QA |
| canonical_alias (snake_case) | registry_artifacts |
{descriptive_snake} |
The canonical alias is used in workflow execution results, eval data directories, and
subagent normalization. It does NOT need to match the PascalCase name — it should be
descriptive of what the agent extracts (e.g., hunt_queries, process_lineage, registry_artifacts).
Also decide:
- UI display name — short human label (e.g., "Registry Artifacts", "Hunt Queries")
- UI scope key — lowercase key for SUBAGENT_SCOPE_MAP (e.g.,
registry,huntqueries) - Icon emoji — for execution modals and eval cards (e.g.,
🗝️)
Integration Checklist
There are 30+ integration points across ~15 files. Read references/integration-checklist.md
for the complete file-by-file guide with code patterns to follow.
The checklist is organized into these layers:
Layer 1: Schema & Config (5 files) — Do These First
These establish the agent's existence in the system. If these are wrong, nothing else works.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 424 lines · 129 tokens per session scan A 95825ff07b12
create-huntable-agent is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 5d ago), licensed MIT. It adds 129 tokens to every session and 6,391 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. 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-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…
configuring-network-segmentation-with-vlans
Designs and implements VLAN-based network segmentation on managed switches to isolate network zones, enforce access control between segments, and reduce the attack surface by limiting lateral movement paths in enterprise network environments.