Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/meltedinhex/analyst-ai-pack/resolving-dynamic-api-hashingnpx skills add meltedinhex/analyst-ai-pack --skill resolving-dynamic-api-hashinggit clone --depth 1 https://github.com/meltedinhex/analyst-ai-packWrote 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/meltedinhex/analyst-ai-pack/resolving-dynamic-api-hashing)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/resolving-dynamic-api-hashing"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/resolving-dynamic-api-hashing.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.00658 |
| Opus 5 | $0.00036 | $0.00329 |
| Sonnet 5 | $0.00014 | $0.00132 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
resolving-dynamic-api-hashing 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 yesterday.
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.
What it actually says
Resolving Dynamic API Hashing
When to Use
- A sample resolves APIs by hash (no plaintext import names) and you have the hash constants from disassembly.
- You need to map each hash back to an API/DLL name to understand functionality.
Do not use this to execute the resolver — it computes hashes over a name wordlist statically and matches them to your observed constants.
Prerequisites
- The hash constants observed in the binary and (optionally) a names wordlist.
Workflow
Step 1: Identify the algorithm
python scripts/analyst.py id 0x6A4ABC5B
Computes the constant under each supported algorithm against a built-in seed list to suggest which algorithm/seed reproduces known API hashes.
Step 2: Resolve hashes against a wordlist
python scripts/analyst.py resolve hashes.txt --algo ror13 --wordlist names.txt
Brute-forces the provided hashes against the wordlist using the chosen algorithm and reports matches.
Step 3: Annotate the disassembly
Label resolved call sites with their API names to recover behavior.
Step 4: Document the routine
Record the algorithm, seed/initial value, and any key so the routine is reusable.
Validation
- The chosen algorithm reproduces at least one known API hash (sanity anchor).
- Resolved names are real exported symbols of plausible DLLs.
- Unresolved hashes are reported, not silently dropped.
Pitfalls
- Wrong endianness/rotation direction producing no matches — try variants.
- Algorithms seeded with a per-sample key; without the key, matches fail.
- Case sensitivity: some routines hash uppercased names, others as-is.
References
- See
references/api-reference.mdfor the resolver. - ATT&CK T1027.007 and the Windows API Index (linked in frontmatter).
What ships with it
3 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.
- yesterday First seen · 89 lines · 71 tokens per session scan A 2c70e4780031
resolving-dynamic-api-hashing is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 658 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects. Use when triaging a suspicious PDF attachment from a phishing email, analyzing a PDF-based exploit document, or building detection signatures for weaponized PDF…
deobfuscating-powershell-obfuscated-malware
Systematically deobfuscate multi-layer PowerShell malware using AST analysis, dynamic tracing, and tools like PSDecode and PowerDecode to reveal hidden payloads and C2 infrastructure.
analyzing-malicious-pdf-with-peepdf
使用 peepdf、pdfid 和 pdf-parser 对恶意 PDF 文档进行静态分析， 提取嵌入的 JavaScript、shellcode 和可疑对象。.
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects.
deobfuscating-powershell-obfuscated-malware
Systematically deobfuscate multi-layer PowerShell malware using AST analysis, dynamic tracing, and tools like PSDecode and PowerDecode to reveal hidden payloads and C2 infrastructure.