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 hiendinhngoc/unknowns --skill blindspotgit clone --depth 1 https://github.com/hiendinhngoc/unknownsWrote 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/hiendinhngoc/unknowns/blindspot)<a href="https://agentmods.dev/skills/hiendinhngoc/unknowns/blindspot"><img src="https://agentmods.dev/badge/skills/hiendinhngoc/unknowns/blindspot/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/hiendinhngoc/unknowns/blindspot"><img src="https://agentmods.dev/badge/skills/hiendinhngoc/unknowns/blindspot.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.00063 | $0.00665 |
| Opus 5 | $0.00032 | $0.00332 |
| Sonnet 5 | $0.00013 | $0.00133 |
| Haiku 4.5 | $0.00006 | $0.00067 |
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 10d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blindspot Pass
Find the unknowns in a system BEFORE touching it. Reconnaissance only.
Read-only. Do not edit, create, or delete any project file. No fixes, however tempting.
Tip for the user (mention once at the start): running this pass in plan mode or a read-only permission mode makes the rule enforced by the harness, not just promised by the model.
Process
- Identify the target. Use the argument or infer the directory/system/feature from conversation. If no target is discernible, ask for one — don't guess.
- Name the domain, derive its dangerous paths. Before scanning, state in one line what kind of system the target is, and list the 2–3 failure classes that domain actually bleeds from. The generic list below is a backend-shaped floor, not a ceiling — a native UI app bleeds from accessibility gaps, lifecycle/identity bugs, and state-restoration loss; a data pipeline from loss, duplication, and ordering; a CLI from argument edge cases and exit codes. Findings should come from the derived list first.
- Explore. Use the agent's file-search/read tools (Glob/Grep/Read,
rg/find/cat, or equivalent) and git log for churn hotspots to understand the target. Look for the domain-derived risks from step 2, plus:- Hidden coupling: modules that import each other's internals, shared mutable state, implicit ordering dependencies
- Unowned edge cases: error paths that swallow exceptions, TODO/FIXME/HACK comments, empty catch blocks
- Stale assumptions: config or constants that encode outdated facts, comments contradicting code, dead feature flags
- Missing tests around dangerous paths: money, auth, deletion, migrations, concurrency — anything irreversible with no test coverage
- Churn hotspots: files with many recent fixes
(
git log --oneline --no-merges -- <path>, ignoring generated files: lockfiles,*.pbxproj, build outputs — their churn is noise)
- Report up to 7 findings, ranked by risk (highest first). If fewer than 5 real risks are found, say so instead of padding.
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.
- 10d ago First seen · 56 lines · 63 tokens per session scan A 7a0e27a0ebd5
blindspot is a skill published in the GitHub repository hiendinhngoc/unknowns (9 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 665 once invoked, about $0.0003 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
fast-resume
Search local coding-agent session history and identify safe resume commands. Use when the user asks to find, inspect, continue, or recover previous work from Claude Code, Codex, Pi, or another agent indexed by fast-resume.
kunpeng-skill
A local research assistant that collects and distills information from projects, websites, apps, media, articles, books, and courses. It turns the material into a searchable library of methods and patterns.
kanban-orchestrator
Kanban orchestrator: decompose, route, verify. No executing.
exploit-xss
Cross-site scripting (XSS) vulnerability detection and exploitation. Supports reflected XSS, stored XSS, DOM-based XSS, and blind XSS testing. Use this skill when user mentions XSS, cross-site scripting, script injection, or needs to test JavaScript injection in parameters, forms, headers, or DOM sources.
results-storage
SQLite-based persistent storage and reporting system for penetration testing results. Use this skill when user needs to store scan results, query vulnerabilities, generate reports, or manage pentest data across sessions.
exploit-sqli
SQL injection detection and exploitation using sqlmap, manual techniques, and custom payloads. Use this skill when user needs to test for SQL injection vulnerabilities, extract database information, or exploit SQLi in parameters, headers, or cookies.