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/healthWrote 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/health)<a href="https://agentmods.dev/commands/marcosd4h/deepextractruntime/health"><img src="https://agentmods.dev/badge/commands/marcosd4h/deepextractruntime/health.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.1 | $0.00000 | $0.01052 |
| Opus 5 | $0.00000 | $0.00526 |
| Sonnet 5 | $0.00000 | $0.00210 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
health 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 7d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Health Check
Overview
Pre-flight validation of the DeepExtractIDA workspace. Checks that extraction data, analysis databases, skill/agent/command registries, and configuration are present and consistent.
Usage:
/health-- standard health check (samples DBs and function indexes at scale)/health --quick-- fast check (skip DB validation and function indexes)/health --full-- exhaustive check (validate every DB, every index, run tests)
Execution
Run .claude/helpers/health_check.py directly from the workspace root. This is the canonical implementation -- do not write inline Python to read or iterate the registries.
python .claude/helpers/health_check.py [--quick|--full] [--json] [--workspace <path>]
The script handles all registry loading and validation internally. Present its stdout output to the user.
Invocation by mode
| Mode | Command |
|---|---|
| Standard | python .claude/helpers/health_check.py |
| Quick (skip DBs + indexes) | python .claude/helpers/health_check.py --quick |
| Full (all DBs + tests) | python .claude/helpers/health_check.py --full |
| JSON output | python .claude/helpers/health_check.py [--quick|--full] --json |
Working directory
The script auto-resolves the workspace root from its own location (.. relative to .claude/helpers/). If running from a non-standard layout, pass --workspace <path> explicitly.
What the script checks
- Extraction Data --
extracted_code/andextracted_dbs/are present with usable modules. - Analysis DBs -- individual
.dbfiles pass schema validation (sampled at scale; all if--full). - Tracking DB --
analyzed_files.dbexists and is valid. - Skills -- every non-methodology skill in
skills/registry.jsonhas a matchingscripts/directory,_common.py, and allentry_scriptson disk. - Agents -- every agent in
agents/registry.jsonhasscripts/,_common.py, and allentry_scriptson disk. - Commands -- every command in
commands/registry.jsonhas its.mdfile and cross-references valid skills/agents. - Configuration --
helpers.config.validate_config()reports no issues. - Function Indexes --
function_index.jsonfiles are valid JSON (sampled at scale; all if--full). - Test Suite --
--fullonly: runspytest tests/ -x -q --tb=shortand reports pass/fail counts.
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.
- 7d ago First seen · 93 lines · 0 tokens per session scan A 5cdd2bb2d535
health is a command published in the GitHub repository marcosd4h/DeepExtractRuntime (19 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,052 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…
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…
fix
Universal debugging and fix application with semantic code analysis.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
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.