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/taintgit 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/taint)<a href="https://agentmods.dev/commands/marcosd4h/deepextractruntime/taint"><img src="https://agentmods.dev/badge/commands/marcosd4h/deepextractruntime/taint.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.04671 |
| Opus 5 | $0.00000 | $0.02336 |
| Sonnet 5 | $0.00000 | $0.00934 |
| Haiku 4.5 | $0.00000 | $0.00467 |
Grade A, and why
taint 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 3d 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taint Analysis
Overview
AI-driven taint analysis: trace attacker-controlled data from entry points to dangerous sinks across module boundaries. Uses LLM agents that navigate taint-enriched callgraphs with trust boundary metadata, read decompiled code on demand, and verify findings against assembly ground truth.
Usage:
/taint <module>-- scan top entry points for taint paths/taint <module> <function>-- scan from a specific function/taint <module> <function> --depth 5-- control callgraph depth/taint <module> --from-entrypoints --top 10-- batch-scan top 10 entry points
IMPORTANT: Execution Model
This command executes immediately. Run the full pipeline and deliver the completed report without pausing for confirmation. Use the workspace handoff pattern for all phases.
Status Messaging (MANDATORY)
Keep the user informed at every phase boundary. Output a plain-text status message before each phase starts and after it completes. Messages are 1-2 lines summarizing what is happening and what the phase produced. Do NOT suppress status messages to "save time."
Execution Context
IMPORTANT: Script invocations like
python .claude/skills/.../script.pyrun from the workspace root. The scripts manage their own path setup.
Step 0: Preflight Validation
from helpers.command_validation import validate_command_args
result = validate_command_args("taint", {
"module": "<user_module>",
"function": "<user_function_or_None>",
})
if not result.ok:
# report errors and stop
db_path = result.resolved["db_path"]
Workspace Protocol
Create .claude/workspace/<module>_taint_<function_or_all>_<timestamp>/ and
pass --workspace-dir and --workspace-step to all skill scripts.
Shell setup rules (required before any redirect):
- Always assign
WORKDIRas an absolute path from the workspace root. - Always
mkdir -p "$WORKDIR/<step_name>"before any>redirect. - Never use
2>&1when capturing--jsonoutput.
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.
- 3d ago First seen · 441 lines · 0 tokens per session scan A 93df4e8bdc75
taint 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 4,671 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.