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/melodic-software/claude-code-plugins/blindspotnpx skills add melodic-software/claude-code-plugins --skill blindspotgit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/melodic-software/claude-code-plugins/blindspot)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/blindspot"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/blindspot.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.1 | $0.00147 | $0.01404 |
| Opus 5 | $0.00073 | $0.00702 |
| Sonnet 5 | $0.00029 | $0.00281 |
| Haiku 4.5 | $0.00015 | $0.00140 |
Grade A, and why
blindspot 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 yesterday.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
Current branch: !git branch --show-current 2>/dev/null || echo "unknown"
Project root: !git rev-parse --show-toplevel 2>/dev/null || echo "unknown"
These values orient this session only; resolve files against the project root while working.
Purpose
Every mode of /discovery:explore builds the AGENT's local knowledge and hands off an EXPLORE.md
artifact. Blindspot mode builds the USER's knowledge and hands off a better prompt, a different
audience and a different deliverable, which is why it is its own skill.
Run it when the user is about to work in territory they don't know, an unfamiliar codebase area OR an unfamiliar domain vocabulary, and the goal is to surface what their framing didn't account for so they can write a sharper implementation prompt. The output is calibrated to the user's disclosed starting point, not to a fixed depth.
Local counterpart discipline to /discovery:explore (what IS in the codebase) and /discovery:research
(what SHOULD BE from external sources): blindspot borrows from both lanes but serves the user's
understanding rather than the agent's.
Workflow
- Intake. Ask the user's starting point first (one question). Blindspot output calibrates to that disclosure. What they already know bounds which gaps are worth surfacing.
- Scan. Two lanes, chosen by what is unfamiliar:
- Codebase lane. Read the target area (the codebase-reading, git-history, and project-structure
dimensions of
${CLAUDE_PLUGIN_ROOT}/skills/explore/SKILL.md) looking specifically for things the user's framing missed: existing patterns they'd duplicate, constraints they'd violate, historical decisions they'd re-litigate, adjacent code their change would break. - Domain lane. Build a lightweight vocabulary ladder grounded in sources fetched this session (repo files, official docs), never bare training recall.
- Codebase lane. Read the target area (the codebase-reading, git-history, and project-structure
dimensions of
- Output. Blindspot cards. One card per blindspot, typed by the kind of gap it is (Landmine / History / Convention / Missing concept): the gap, why it matters here, and a copyable prompt-fix line. Close by assembling the fixes into ONE improved implementation prompt the user can run next.
- Escalate when depth warranted, a domain too deep for a lightweight ladder gets a recommendation
to run proper external research (
/discovery:research) or whatever structured-learning capability the environment provides.
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.
- yesterday First seen · 96 lines · 147 tokens per session scan A 5d8cd64df381
blindspot is a skill published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), licensed MIT. It adds 147 tokens to every session and 1,404 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
count-combinations
For probability and counting: permutations, combinations, sample spaces, Monte Carlo simulation, brute-force enumeration, card/dice problems.
career-path-planner
Career goal mapping with skill gap analysis, actionable development plans, and milestone tracking. Use when planning career transitions, identifying skill gaps, setting professional development goals, or evaluating career options.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
course-material-creator
Create custom educational materials including syllabi, lesson plans, assessments, reading lists, and learning objectives. Use when building course curricula, training programs, workshops, or educational content.
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…