Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/marcosd4h/DeepExtractRuntimenpx agentmods add skills/marcosd4h/deepextractruntime/function-indexWrote 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/function-index)<a href="https://agentmods.dev/skills/marcosd4h/deepextractruntime/function-index"><img src="https://agentmods.dev/badge/skills/marcosd4h/deepextractruntime/function-index/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/marcosd4h/deepextractruntime/function-index"><img src="https://agentmods.dev/badge/skills/marcosd4h/deepextractruntime/function-index.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.00117 | $0.03521 |
| Opus 5.5 | $0.00047 | $0.01408 |
| Sonnet 5.5 | $0.00023 | $0.00704 |
| Haiku 4.5 | $0.00012 | $0.00352 |
Grade A, and why
function-index 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 1mo 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Function Index
Purpose
Provide fast function-to-file resolution for DeepExtractIDA extraction outputs. Every extracted module folder contains a function_index.json that maps each function name to the .cpp file containing its decompiled output, plus a library tag for boilerplate detection. This skill provides scripts to query, filter, and resolve these indexes without scanning hundreds of .cpp files.
This skill is designed to be reused by other skills -- it does not depend on any other skills.
When NOT to Use
- Extracting full function data (decompiled code, assembly, xrefs) -- use decompiled-code-extractor
- Classifying functions by purpose or computing interest scores -- use classify-functions
- Searching across strings, APIs, and classes (not just function names) -- use
unified_search.pyor decompiled-code-extractor - Understanding what a function does -- use re-analyst or
/explain - Tracing call chains between functions -- use callgraph-tracer
Data Sources
Each module folder under extracted_code/{module}/ contains:
function_index.json-- lightweight index mapping function names to files and library tagsfile_info.json-- full module metadata (signatures, imports, exports, etc.){module}_*.cpp-- grouped decompiled source files
function_index.json Format
{
"<function_name>": {
"file": "module_standalone_group_5.cpp",
"library": null
},
"<wil_function>": {
"file": "module_standalone_group_1.cpp",
"library": "WIL"
}
}
| Field | Description |
|---|---|
file |
The .cpp filename in the same directory as the index |
library |
Library tag: WIL, STL, WRL, CRT, ETW/TraceLogging, or null |
library = null means application code. Non-null tags identify known library/runtime boilerplate.
What ships with it
6 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.
- 1mo ago Changed · +9 lines c4ea7a1a17e6
- 1mo ago First seen · 296 lines · 117 tokens per session scan A ea9af28de830
function-index is a skill published in the GitHub repository marcosd4h/DeepExtractRuntime (21 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 3,521 once invoked, about $0.0005 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…