hmbown/see-invisibility
generated/hermes/investigation-and-preparation/see-invisibility/SKILL.md
In D&D, See Invisibility lets you see creatures and objects that have been made invisible. The real-world version is revealing deliberate obscurity: finding the hidden costs in a pricing page, uncovering the actual terms buried in a EULA, identifying the obfuscated tracking in a codebase, or surfacing the real behavior behind a misleading UI. Unlike Perception (which notices what is overlooked) or True Seeing (which pierces all illusion), See Invisibility specifically targets things that were hidden on purpose.
$ install --global
skillsauthnpx skillsauth add hmbown/wizards-of-the-ghosts see-invisibilityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:36 PM1.8s1 file scanned
SKILL.md
- name:
- see-invisibility
- description:
- In D&D, See Invisibility lets you see creatures and objects that have been made invisible. The real-world version is revealing deliberate obscurity: finding the hidden costs in a pricing page, uncovering the actual terms buried in a EULA, identifying the obfuscated tracking in a codebase, or surfacing the real behavior behind a misleading UI. Unlike Perception (which notices what is overlooked) or True Seeing (which pierces all illusion), See Invisibility specifically targets things that were hidden on purpose.
- version:
- 1.0.0
- author:
- Wizards of the Ghosts
- license:
- CC0-1.0
- compatibility:
- Hermes Agent skills system
See Invisibility
Reveal what has been deliberately hidden, obscured, or made hard to find.
What This Skill Does
In D&D, See Invisibility lets you see creatures and objects that have been made invisible. The real-world version is revealing deliberate obscurity: finding the hidden costs in a pricing page, uncovering the actual terms buried in a EULA, identifying the obfuscated tracking in a codebase, or surfacing the real behavior behind a misleading UI. Unlike Perception (which notices what is overlooked) or True Seeing (which pierces all illusion), See Invisibility specifically targets things that were hidden on purpose. In this grimoire, See Invisibility is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: See Invisibility (spell).
When To Use
- You suspect something is being deliberately hidden or obscured: hidden fees, buried terms, obfuscated code, or misleading UI.
- A system or document seems designed to make certain information hard to find.
- You want to audit a product, contract, or codebase for deliberately obscured behavior.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify the context where something might be deliberately hidden.
- Look for the signs of intentional obscurity: complexity that serves no user, deep nesting, misleading labels, dark patterns.
- Extract and surface what was hidden, with evidence of the obscuring mechanism.
- Deliver the findings with a clear distinction between confirmed hidden elements and suspicious-but-unconfirmed patterns.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A list of deliberately hidden or obscured elements, with the mechanism used to hide each one.
- Evidence for each finding: why this appears intentionally hidden rather than merely overlooked.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Distinguish between intentional obscurity and accidental complexity. Not everything hard to find was hidden on purpose.
- Do not assume malice without evidence. Surface the hidden elements and let the user judge intent.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
Example Invocation
/see-invisibility Use \$see-invisibility to audit this [product/contract/codebase/page] for deliberately hidden or obscured elements. What has been made hard to find on purpose?
Related Skills
hmbown/zone-of-truth
testing
VerifiedTrustedCommunity
Enter a mode where every assertion is backed by evidence, confidence is calibrated, speculation is flagged, and hallucination is actively resisted.
55SKILL.mdUpdated Apr 5, 2026
hmbown/vicious-mockery
development
VerifiedTrustedCommunity
The bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report that makes the PM cancel the launch, the code review that makes the author delete the PR, the roast that makes the founder pivot. The damage is the point.
55SKILL.mdUpdated Apr 5, 2026
hmbown/unseen-servant
tools
VerifiedTrustedCommunity
Use this spell when you need a tireless helper that organizes, tidies, triages, and maintains without requiring your constant attention.
55SKILL.mdUpdated Apr 5, 2026
hmbown/true-strike
testing
VerifiedTrustedCommunity
Use this spell for preflight certainty: dry runs, validation checks, dependency verification, and rehearsals that make the next deploy, query, or command much more likely to succeed. It trades a little time up front for fewer blind swings and fewer expensive misses.
55SKILL.mdUpdated Apr 5, 2026