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 skills/echoo19/decision-simulator/detect-context-gapsnpx skills add echoo19/decision-simulator --skill detect-context-gapsgit clone --depth 1 https://github.com/echoo19/decision-simulatorWrote 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/echoo19/decision-simulator/detect-context-gaps)<a href="https://agentmods.dev/skills/echoo19/decision-simulator/detect-context-gaps"><img src="https://agentmods.dev/badge/skills/echoo19/decision-simulator/detect-context-gaps.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.00076 | $0.00519 |
| Opus 5 | $0.00038 | $0.00260 |
| Sonnet 5 | $0.00015 | $0.00104 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
detect-context-gaps 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detect Context Gaps
Find the missing inputs that materially affect the decision. Do not ask for a long generic questionnaire.
Method
- Restate the current decision and provisional recommendation.
- Identify which assumptions are carrying the answer.
- Flag unknowns that could materially change the ranking of options.
- Explain the risk created by each unknown.
- Prefer the cheapest clarifying question, measurement, or experiment that reduces uncertainty.
Focus Areas
Check for gaps in:
- real traffic or scale assumptions
- failure tolerance and recovery expectations
- latency or throughput requirements
- data sensitivity and compliance constraints
- ownership and team boundaries
- rollout and migration constraints
- testing and observability maturity
- dependency constraints and platform limits
- time horizon: quick patch versus long-lived system
- reversibility: how painful it is to undo the choice
Quality Bar
- Only ask for information that changes the decision, confidence, or rollout plan.
- Name the consequence of not knowing.
- Distinguish
[assumption],[unknown], and[nice-to-know]. - If the answer is still directionally clear despite gaps, say so.
Suggested Output
Current decision frame
State the decision and the current leaning.
Critical unknowns
List the few unknowns that could change the recommendation. Tag each as [unknown] or [nice-to-know].
Example:
[unknown]Whether existing integrations depend on undocumented frontend-only behavior — if yes, backend-first migration cost doubles[nice-to-know]Current p99 latency under load — would affect which caching option to prefer but not the core recommendation
Hidden assumptions
List the assumptions currently doing too much work. Tag each as [assumption].
Example:
[assumption]Team has capacity to migrate existing callers within one sprint — if false, the recommended path requires a compatibility layer
Risk of deciding now
Explain what could go wrong if the decision is made without resolving the gaps.
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 · 68 lines · 76 tokens per session scan A d4d22a3bf7bc
detect-context-gaps is a skill published in the GitHub repository echoo19/decision-simulator (4 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 519 once invoked, about $0.0004 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…