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 gnurio/nurijanian-skills --skill blind-spot-scangit clone --depth 1 https://github.com/gnurio/nurijanian-skillsWrote 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/gnurio/nurijanian-skills/blind-spot-scan)<a href="https://agentmods.dev/skills/gnurio/nurijanian-skills/blind-spot-scan"><img src="https://agentmods.dev/badge/skills/gnurio/nurijanian-skills/blind-spot-scan/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/gnurio/nurijanian-skills/blind-spot-scan"><img src="https://agentmods.dev/badge/skills/gnurio/nurijanian-skills/blind-spot-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00164 | $0.01842 |
| Opus 5.5 | $0.00066 | $0.00737 |
| Sonnet 5.5 | $0.00033 | $0.00368 |
| Haiku 4.5 | $0.00016 | $0.00184 |
Grade A, and why
blind-spot-scan 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blind Spot Scan
Read references/pm-excellence-behaviors.md before beginning. You will be probing across all
7 clusters systematically, looking for the gaps the PM cannot see because they're inside them.
What This Mode Does
You run a targeted behavioral interview — 12 questions designed to reveal systematic patterns, not just one-off failures. From their answers, you identify which behavioral clusters they're systematically weak in, and — crucially — why those gaps are invisible to them.
The output is a prioritized list of 2-4 blind spots, each explained with: what it is, why they can't see it, what it costs them, and one concrete thing to do about it.
Why Blind Spots Are Hard to See
Most PM blind spots are invisible for structural reasons — not because the PM is unaware, but because the feedback system around them is broken:
- Competence blind spots: Things they're genuinely good at in other domains that don't transfer to PM — they think they're good at X because they were good at it before
- Approval loop blind spots: Behaviors that get positive signals from leadership but erode team trust — they optimize for the wrong feedback
- Narrative blind spots: Stories they've told about themselves enough times that the story has replaced reality ("I'm a great communicator" covers a lot of terrain)
- Anti-pattern blind spots: The behaviors in the source material that teammates find disqualifying — PMs rarely hear these directly
Your job is to find the gap between how they describe themselves and what the behaviors they describe actually reveal.
Process
Step 1: Frame the Session
Tell the PM: "I'm going to ask you 12 questions. Some will feel easy. Some won't. Answer as honestly as you can about how things actually are — not how you'd want them to be or how you perform in interviews. The goal isn't to catch you out — it's to find the gaps you can't see because you're inside them."
Step 2: The 12-Question Interview
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.
- 1mo ago First seen · 174 lines · 164 tokens per session scan A cd541f07c00f
blind-spot-scan is a skill published in the GitHub repository gnurio/nurijanian-skills (127 stars, last pushed 2mo ago), licensed MIT. It adds 164 tokens to every session and 1,842 once invoked, about $0.0007 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.