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 commands/marcosd4h/deepextractruntime/full-reportgit 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/full-report)<a href="https://agentmods.dev/commands/marcosd4h/deepextractruntime/full-report"><img src="https://agentmods.dev/badge/commands/marcosd4h/deepextractruntime/full-report.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.00000 | $0.02747 |
| Opus 5 | $0.00000 | $0.01373 |
| Sonnet 5 | $0.00000 | $0.00549 |
| Haiku 4.5 | $0.00000 | $0.00275 |
Grade A, and why
full-report 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Analysis Report
Overview
End-to-end analysis of a DeepExtractIDA module combining multiple analysis passes: binary identity, function classification, attack surface mapping, call graph topology, and specialized analysis (COM, global state). This is the most thorough single-command analysis.
The text after /full-report is the module name (e.g., /full-report appinfo.dll). Add --brief for an abbreviated version. If omitted, list available modules and ask.
IMPORTANT: Execution Model
This is an execute-immediately command. Do NOT present anything for user confirmation. Run and write the final 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
This command orchestrates many skills; always use filesystem handoff:
- At setup time, create
.claude/workspace/<module>_full_report_<timestamp>/. - For every skill execution in all phases, pass:
--workspace-dir <run_dir>--workspace-step <phase_or_step_name>
- Treat script stdout as summary-only.
- Read full intermediate results only from
<run_dir>/<step_name>/results.jsonwhen synthesizing the final report. - Use
<run_dir>/manifest.jsonto confirm completed/failed steps and avoid context blowup from large JSON payloads.
Steps
Step 0: Preflight Validation
Validate arguments using helpers.command_validation.validate_command_args("full-report", {"module": "<module>"}).
If validation fails, report the errors and stop. On success, use result.resolved["db_path"] for subsequent script calls.
Setup
- Find the module DB
Use the decompiled-code-extractor skill (
find_module_db.py) to resolve the module.
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 · 194 lines · 0 tokens per session scan A 8dffb4c69edb
full-report is a command published in the GitHub repository marcosd4h/DeepExtractRuntime (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,747 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.