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.
git 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/commands/marcosd4h/deepextractruntime/compare-modules)<a href="https://agentmods.dev/commands/marcosd4h/deepextractruntime/compare-modules"><img src="https://agentmods.dev/badge/commands/marcosd4h/deepextractruntime/compare-modules/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/compare-modules"><img src="https://agentmods.dev/badge/commands/marcosd4h/deepextractruntime/compare-modules.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.01960 |
| Opus 5.5 | $0.00000 | $0.00784 |
| Sonnet 5.5 | $0.00000 | $0.00392 |
| Haiku 4.5 | $0.00000 | $0.00196 |
Grade A, and why
compare-modules 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compare Modules
Overview
Cross-module analysis of two or more DeepExtractIDA-analyzed modules -- comparing dependency relationships, import/export overlap, function classification distributions, and cross-module call chains.
The text after /compare-modules lists two or more module names:
/compare-modules appinfo.dll cmd.exe/compare-modules explorer.exe shell32.dll ntdll.dll/compare-modules --all-- compare all analyzed modules at a high level (capped at 200 modules; see Scale Limits)
If fewer than two modules are specified, list available modules and ask.
Scale Limits
The --all flag is capped at 200 modules (configurable via scale.max_modules_compare in .claude/config/defaults.json). If there are more than 200 modules, --all compares the first 200 and warns the user. For targeted comparison of specific modules, always list them explicitly.
With 100+ modules, pairwise analysis becomes O(N^2). Use --all only for high-level overviews; use explicit module lists for detailed comparison.
IMPORTANT: Execution Model
This is an execute-immediately command. Do NOT present anything for user confirmation. Run and write the final comparison report straight to the chat as your response. The user expects to see the completed report.
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.
Workspace Protocol
For multi-module comparison:
- Create a top-level run directory under
.claude/workspace/for the command. - Create per-module sub-runs (for example,
<run_dir>/<moduleA>/,<run_dir>/<moduleB>/) to avoid collisions. - Pass
--workspace-dir <module_run_dir>and--workspace-step <step_name>to every skill invocation. - Keep only compact summaries in context; avoid inlining full JSON across modules.
- Read detailed data on demand from
<module_run_dir>/<step_name>/results.jsonand use each run'smanifest.jsonfor traceability.
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 First seen · 123 lines · 0 tokens per session scan A 67e7c43c3680
compare-modules 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 1,960 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.