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/.cursor/skills/mdu/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/mdu)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/mdu"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/mdu/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/mdu"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/mdu.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.00203 | $0.03055 |
| Opus 5 | $0.00102 | $0.01528 |
| Sonnet 5 | $0.00041 | $0.00611 |
| Haiku 4.5 | $0.00020 | $0.00305 |
Grade A, and why
mdu 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 11d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDU -- Markdown Documentation Updater
Update all Markdown documentation to accurately reflect the current state of the codebase. The goal is factual alignment between code and docs -- not stylistic polish.
Philosophy
Documentation is subordinate to code. When docs and code disagree, code wins. This skill exists to close that gap efficiently: read the diff, update only affected docs, verify the build.
Scope boundaries
In scope: docs/CHANGELOG.md, README.md, all files under docs/, mkdocs.yml nav entries.
Off limits: AGENTS.md and CLAUDE.md are manually maintained -- never modify them. They define the agent operating contract and are outside the documentation update cycle.
Standard run
When the user says "mdu" or asks to update/sync docs, follow this sequence.
Step 1: Detect what changed
Understand the scope of recent changes before touching any docs.
# On a feature branch:
git diff main..HEAD --name-only
git log main..HEAD --oneline
# On main after recent commits:
git diff HEAD~3..HEAD --name-only
git log --oneline -5
Map each changed file to its documentation surface using this routing:
| Change type | Docs to check | Link check? |
|---|---|---|
| UI or page behavior | Feature docs, guides, README quick-start | No |
| API endpoints or behavior | docs/reference/api.md, relevant guides |
No |
| Workflow execution or state | docs/architecture/workflow-data-flow.md, feature docs |
No |
| Workflow config / presets | docs/getting-started/configuration.md, preset README |
No |
| Database models or schemas | docs/reference/schemas.md |
No |
| Source ingestion or scraping | docs/guides/source-config.md, docs/guides/add-feed.md |
No |
| Tests or test infra | docs/development/testing.md |
No |
| CLI commands | docs/reference/cli.md |
No |
| MCP tools | docs/reference/mcp-tools.md |
No |
| ML / model changes | docs/ml-training/, docs/reference/ml-features.md |
No |
| New dependencies | README (stack section), relevant setup/install docs | No |
| New doc page created | All docs that reference the same feature | Yes -- grep for bare text references that should now be links |
| Existing page renamed or moved | mkdocs.yml, all docs |
Yes -- grep for old filename/path |
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.
- 11d ago First seen · 235 lines · 203 tokens per session scan A 0ae5920a91dc
mdu is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 3d ago), licensed MIT. It adds 203 tokens to every session and 3,055 once invoked, about $0.0010 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-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…