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/marcosd4h/deepextractruntime/import-export-resolvernpx skills add marcosd4h/DeepExtractRuntime --skill import-export-resolvergit clone --depth 1 https://github.com/marcosd4h/DeepExtractRuntimeWrote 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/marcosd4h/deepextractruntime/import-export-resolver)<a href="https://agentmods.dev/skills/marcosd4h/deepextractruntime/import-export-resolver"><img src="https://agentmods.dev/badge/skills/marcosd4h/deepextractruntime/import-export-resolver.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.00111 | $0.02221 |
| Opus 5 | $0.00056 | $0.01111 |
| Sonnet 5 | $0.00022 | $0.00444 |
| Haiku 4.5 | $0.00011 | $0.00222 |
Grade A, and why
import-export-resolver 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 4d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import/Export Resolution
Purpose
Resolve PE-level import and export relationships across all analyzed
modules. This skill works from the PE import/export tables stored in
file_info.imports and file_info.exports -- the authoritative record
of what the Windows loader resolves at load time.
This is distinct from code-level xrefs (simple_outbound_xrefs) that
callgraph-tracer uses. PE tables are ground truth for loader-level
dependencies; xrefs capture what IDA found in the disassembly. Use this
skill for loader-level questions, callgraph-tracer for code-level
call chains.
When NOT to Use
- Tracing code-level call chains or cross-module execution paths -- use callgraph-tracer
- Categorizing imports by API type (file I/O, crypto, network, etc.) -- use generate-re-report (
analyze_imports.py) - Mapping attack surface or ranking entry points by risk -- use map-attack-surface
- General function explanation or decompiled code analysis -- use re-analyst or
/explain - Understanding cross-module data flow (taint propagation, parameter tracing) -- use taint-analysis or data-flow-tracer
Data Sources
SQLite Databases (primary)
file_info.imports-- PE import table (JSON). Each entry hasmodule_name,functions[]withfunction_name,is_delay_loaded,ordinal. API-set names are resolved to real DLLs.file_info.exports-- PE export table (JSON). Each entry hasfunction_name,ordinal,is_forwarded,forwarded_to.analyzed_files.db-- tracking DB for module discovery.
See data_format_reference.md and file_info_format_reference.md for full JSON schemas.
Finding a Module DB
python .claude/skills/decompiled-code-extractor/scripts/find_module_db.py --list
python .claude/skills/decompiled-code-extractor/scripts/find_module_db.py appinfo.dll
Utility Scripts
query_function.py -- Resolve Function Importers/Exporters (Start Here)
What ships with it
7 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.
- 4d ago First seen · 263 lines · 111 tokens per session scan A 0a21471c43a4
import-export-resolver is a skill published in the GitHub repository marcosd4h/DeepExtractRuntime (19 stars, last pushed 4mo ago), licensed MIT. It adds 111 tokens to every session and 2,221 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…