Borrowing it
Nothing to install: this file belongs to inspecto-dev/inspecto. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/inspecto-dev/inspecto/main/.claude/skills/vscode-ext-probe/extract-context/SKILL.mdgit clone --depth 1 https://github.com/inspecto-dev/inspectoWrote 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/skills/inspecto-dev/inspecto/extract-context)<a href="https://agentmods.dev/skills/inspecto-dev/inspecto/extract-context"><img src="https://agentmods.dev/badge/skills/inspecto-dev/inspecto/extract-context/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/skills/inspecto-dev/inspecto/extract-context"><img src="https://agentmods.dev/badge/skills/inspecto-dev/inspecto/extract-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 20 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
- high Data Exfiltration · line 23 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00098 | $0.00357 |
| Opus 5.5 | $0.00039 | $0.00143 |
| Sonnet 5.5 | $0.00020 | $0.00071 |
| Haiku 4.5 | $0.00010 | $0.00036 |
Grade A, and why
vscode-ext-context 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 2mo 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.
What it actually says
Extract VSCode Extension Command Context
Get raw source code around a command's registerCommand for manual analysis.
Usage
# Extract context for a specific command
python3 scripts/extract_context.py <extension-id> <command-name> [--chars 1500]
# Extract context for a keyword (not just commands)
python3 scripts/extract_context.py <extension-id> --keyword "handleUri" [--chars 2000]
# Search for any pattern in extension.js
python3 scripts/extract_context.py <extension-id> --pattern "sendText.*true" [--chars 500]
What It Does
Reads the extension's minified extension.js and extracts surrounding characters around:
- A specific
registerCommand("name"call - A keyword occurrence
- A regex pattern match
This is the "escape hatch" for when automated analysis doesn't capture enough detail. Use it to:
- See the full function body of a command handler
- Trace how parameters flow through internal functions
- Find related patterns (e.g., all
sendTextcalls to determine auto-send behavior) - Inspect URI handler implementations
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 44 lines · 98 tokens per session scan A d5962f994713
vscode-ext-context is a skill published in the GitHub repository inspecto-dev/inspecto (22 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 357 once invoked, about $0.0004 per session on Opus 5.5. 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 skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
dex-doctor
Whole-system checkup: verifies every Dex feature honestly (working/off/broken/couldn't-check), self-heals what's provably safe, guides the rest. Use when the user says 'is Dex healthy', 'something's broken', 'check my setup', 'run diagnostics'. Not for discovering unused features; use dex-level-up. Not for applying an…
debug-helper
Help debug code by analyzing error messages, identifying root causes, and providing fix suggestions.