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/huntable-doc-trueup/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/huntable-doc-trueup)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/huntable-doc-trueup"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/huntable-doc-trueup/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/huntable-doc-trueup"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/huntable-doc-trueup.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00156 | $0.04042 |
| Opus 5 | $0.00078 | $0.02021 |
| Sonnet 5 | $0.00031 | $0.00808 |
| Haiku 4.5 | $0.00016 | $0.00404 |
Grade C, and why
huntable-doc-trueup scanned grade C 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 12d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
grep -RInE '<!-- (AUDIT:|TODO: verify)' docs --include='*.md' || true ``` Resolve every marker you find. If the claim is verified wrong, correct the visible prose and strip the marker. If it remains genuinely unverifiabl How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
huntable-doc-trueup
A systematic, sequential documentation audit for Huntable CTI Studio. You verify first, then rewrite — never the other way around. Your corrections are factual only: wrong paths, stale names, broken examples, missing required steps. Not style, not polish.
Neighboring skills — pick the right one:
- doc-overhaul — deep restructuring, fluff cuts, page deletions, writing missing docs. That skill has deletion and rewrite authority; this one is the frequent, safe drift-correction pass.
- mdu — updates docs to reflect changes made in the current session. huntable-doc-trueup audits the whole doc set against the whole codebase, regardless of what this session touched.
- mkdocs-helper — single-file editorial review. huntable-doc-trueup is the full-repo factual sweep.
A note on trust: this skill file itself contains repo facts (paths, names, commands) that go stale like any doc. Where possible the phases below tell you to enumerate live state instead of trusting a list. If you find a claim in this skill that contradicts the repo (a missing file, a renamed agent), the repo wins — and note the skill drift in your final report so the operator can fix the skill.
Phase 1 — Load Oracles (do this first, before touching any doc)
Before reading or editing docs, run git status --short and record every pre-existing
modified or untracked path. Do not edit, stage, or otherwise absorb parallel work; stage only
explicit doc paths if a later commit is requested.
Read these files. They are the ground truth you validate docs against. They change often enough that stale docs are the default, not the exception.
src/database/models.py — model names, field names, table names
src/config/workflow_config_schema.py — config keys, agent names, workflow step IDs
src/web/routes/__init__.py — all registered API routes and prefixes
src/worker/celery_app.py — scheduled task names, beat schedule
tests_runner/config.py — valid test suite names (`RunTestType`)
tests_runner/cli.py — test CLI flags and argument handling
pyproject.toml — package version, dependency versions
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.
- 12d ago First seen · 334 lines · 156 tokens per session scan C a55b94203df3
huntable-doc-trueup is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 4d ago), licensed MIT. It adds 156 tokens to every session and 4,042 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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.