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 commands/marcosd4h/deepextractruntime/explainWrote 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/commands/marcosd4h/deepextractruntime/explain)<a href="https://agentmods.dev/commands/marcosd4h/deepextractruntime/explain"><img src="https://agentmods.dev/badge/commands/marcosd4h/deepextractruntime/explain/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/commands/marcosd4h/deepextractruntime/explain"><img src="https://agentmods.dev/badge/commands/marcosd4h/deepextractruntime/explain.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.00000 | $0.02264 |
| Opus 5.5 | $0.00000 | $0.00906 |
| Sonnet 5.5 | $0.00000 | $0.00453 |
| Haiku 4.5 | $0.00000 | $0.00226 |
Grade A, and why
explain 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain Function
Overview
Get a quick, structured explanation of what a decompiled function does -- its purpose, parameters, key API calls, data flow, and call context -- without running a full audit or trace pipeline.
The text after /explain specifies the function name and optionally the module:
/explain AiLaunchProcess-- searches all modules/explain appinfo.dll AiLaunchProcess-- targets specific module/explain appinfo.dll AiLaunchProcess --depth 2-- include callee code 2 levels deep/explain appinfo.dll --search LaunchProcess-- pattern search
If no function is specified, ask the user.
Default callee depth is 1 (direct callees only). Override with --depth N (0 = no callees, 2 = callees of callees, etc.). The script performs true BFS recursive traversal through the call chain, filtering boilerplate (WIL/CRT/ETW thunks) automatically.
IMPORTANT: Execution Model
This is an execute-immediately command. Do NOT present anything for user confirmation. Run and write the final explanation straight to the chat as your response. The user expects to see the completed output.
Execution Context
IMPORTANT: Any inline Python that imports
helpers.*must run withcd <workspace>/.claude(so the.claude/directory is onsys.path), not from the workspace root. Script invocations likepython .claude/skills/.../script.pycan be run from the workspace root because those scripts manage their own path setup.
Steps
Step 0: Preflight Validation
Validate arguments using helpers.command_validation.validate_command_args("explain", {"module": "<module>", "function": "<function>"}).
If validation fails, report the errors and stop. On success, use result.resolved["db_path"] for subsequent script calls.
- Locate the function
Quick lookup: Use
python .claude/skills/function-index/scripts/lookup_function.py <function_name>to locate the function across all modules instantly. Cross-dimensional search: When the search term might match a string, API call, or class name, usepython .claude/helpers/unified_search.py <db_path> --query <term>to search all dimensions at once. Otherwise, use the decompiled-code-extractor skill (find_module_db.pythenlist_functions.py --search) to resolve the module DB and exact function name.
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 · +4 lines d5bea9431fef
- 1mo ago Changed e3a4b0444b51
- 1mo ago First seen · 142 lines · 0 tokens per session scan A 952f70b39701
explain is a command published in the GitHub repository marcosd4h/DeepExtractRuntime (21 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,264 tokens. 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.