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 skills add emaraschio/cursor-commands --skill blind-spot-passgit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/emaraschio/cursor-commands/blind-spot-pass)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/blind-spot-pass"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/blind-spot-pass/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/emaraschio/cursor-commands/blind-spot-pass"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/blind-spot-pass.svg" alt="Reviewed on agentmods" width="80" 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.00138 | $0.02350 |
| Opus 5.5 | $0.00055 | $0.00940 |
| Sonnet 5.5 | $0.00028 | $0.00470 |
| Haiku 4.5 | $0.00014 | $0.00235 |
Grade A, and why
blind-spot-pass 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 1mo 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blind spot pass
Role
You run a blind spot pass before building. The user gives a rough plan, goal, or prompt; you treat it as the map and the real project as the territory. You classify what is known and unknown across four quadrants, then ask the highest-leverage interview questions so building does not start on hidden assumptions.
This skill uses a two-step handshake: (1) deliver the pass and wait for pass approval; (2) build only after a later explicit execute now (or equivalent), or when the user explicitly says to skip the pass and build now. Pass approval is not build. This skill is plan-only on delivery and on pass approval.
When to use
Use before writing, coding, product specs, or any build where the prompt may be incomplete. Run this when the user wants to find unknowns or surface unstated context before the agent acts. For a greenfield fog map with parallel tracks, use pathfinder. For a six-part delegation contract, use define-agent-goal. For a runnable prompt, use structure-prompt. For a technical audit of a step-by-step implementation plan, use a dedicated plan-preflight skill, not this one.
Intensity
| Intensity | When |
|---|---|
| standard (default) | Always, unless the user requests red-team |
| red-team | Only when the user asks to challenge, break, or red-team the plan |
There is no light mode. Detection phrases for red-team include: challenge, break, red-team, red team, find why this fails, stress-test the ask.
Under red-team, still deliver the four-quadrant pass and interview questions. Actively seek reasons the map (ask) fails, and push harder on §4 sub-bullets and high-leverage questions. Do not replace the pass with a free-form principal-engineer risk report or a step-by-step plan audit (that is plan-preflight skill work).
Workflow
Run phases in order. Do not deliver the pass until Phase 3. Do not execute the task, scaffold code, or run destructive commands when delivering the pass, when the user only approves the pass, or unless the user explicitly says to skip the pass and build now.
What ships with it
3 files 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.
- 1mo ago First seen · 152 lines · 138 tokens per session scan A 4b8c2fb5fc0a
blind-spot-pass is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 5d ago), licensed MIT. It adds 138 tokens to every session and 2,350 once invoked, about $0.0006 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-31.
Other skills, from other repositories
review-all
Use when the user asks for a deep review, full review, comprehensive review, production readiness assessment, full audit, multi-domain audit, "security and reliability and code review", or "review everything". Also use when the user explicitly requests performance review alongside the comprehensive request (e.g.…
active-review
Use when the user wants to prepare for a manual PR code review and asks for help targeting it — a terse PR summary, ranked files to read first, and paste-ready inline comment drafts with GitHub deep-links. Triggers: "active review this PR", "walk me through this PR", "help me review this", "give me inline comments to…
review-documentation
Use when the user asks for a documentation review, doc audit, doc comment review, godoc review, proto comment review, OpenAPI or Swagger spec review, README review, example test review, "are the docs in sync with the code", "do the docs still match", "are these comments accurate", or "check the examples". Also use…
review-api-compat
Use when the user asks for an API compatibility review, breaking change review, proto breaking change review, buf breaking review, OpenAPI compatibility check, gRPC backwards compatibility audit, "are these API changes breaking", "did we break the wire", contract evolution review, or backwards-compatibility audit on…
review-reliability
Use when the user asks for a reliability review, production readiness assessment, stability analysis, graceful shutdown audit, drain or rollout review, timeout review, timeout budget check, deadline propagation review, circuit breaker or bulkhead review, retry and backoff review, goroutine leak or resource leak…
discover-patterns
Use when exploring a new codebase's architecture, auditing codebase consistency, generating a patterns document, or preparing input for conformance checking during code review.