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/auditgit clone --depth 1 https://github.com/marcosd4h/DeepExtractRuntimeWhat 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.09270 |
| Opus 5 | $0.00000 | $0.04635 |
| Sonnet 5 | $0.00000 | $0.01854 |
| Haiku 4.5 | $0.00000 | $0.00927 |
Grade A, and why
audit 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 2d 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 — 607 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Overview
Perform a focused security audit of a specific function -- building a comprehensive security dossier, tracing attack reachability, and reporting findings with risk assessment and recommendations.
The text after /audit specifies the function name and optionally the module:
/audit AiCheckSecureApplicationDirectory-- searches all modules/audit appinfo.dll AiCheckSecureApplicationDirectory-- targets specific module/audit appinfo.dll --search CheckSecurity-- pattern search/audit appinfo.dll AiLaunchProcess --diagram-- include Mermaid call graph diagram
If no function is specified, ask the user.
IMPORTANT: Execution Model
This is an execute-immediately command. Do NOT present anything for user confirmation Run and write the final audit report straight to the chat as your response. The user expects to see the completed report.
Workspace Protocol
Before running the multi-skill audit pipeline:
- Create a run directory under
.claude/workspace/(for example,.claude/workspace/<module>_audit_<function>_<timestamp>/). - Run every skill script with:
--workspace-dir <run_dir>--workspace-step <step_name>
- Keep only compact summaries in context/chat output.
- Read full details only on demand from:
<run_dir>/<step_name>/results.json<run_dir>/<step_name>/summary.json
- Use
<run_dir>/manifest.jsonas the source of truth for completed steps. - Staleness check (when reusing an existing workspace): If a workspace directory already exists and
manifest.jsonshows all steps withstatus: success, check freshness before reusing results:- Read
manifest.jsoncreated_attimestamp. - Compare against the analysis DB file modification time (
mtimeof the.dbfile resolved in Step 0). - If the DB
mtimeis newer thanmanifest.created_at, warn the user: "Workspace was created before the current DB was last modified. Results may be outdated. Re-run with--no-cacheto regenerate all steps." Then proceed with the stale results unless the user explicitly requests regeneration. - If the workspace is older than 24 hours (regardless of DB age), emit an informational note at the start of the report: "Note: Workspace is N hours old. Results may be stale if the extraction has been re-run since creation."
- These are warnings only — do not block execution. The user decides whether to re-run.
- Read
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.
- 2d ago First seen · 607 lines · 0 tokens per session scan A 5e8481cf12a1
audit is a command published in the GitHub repository marcosd4h/DeepExtractRuntime (20 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,270 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.