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 Wondermonger-daydreaming/claude-skills-library --skill trans-architectural-blind-spot-detectiongit clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-libraryWrote 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/wondermonger-daydreaming/claude-skills-library/trans-architectural-blind-spot-detection)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/trans-architectural-blind-spot-detection"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/trans-architectural-blind-spot-detection/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/wondermonger-daydreaming/claude-skills-library/trans-architectural-blind-spot-detection"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/trans-architectural-blind-spot-detection.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.00143 | $0.02686 |
| Opus 5.5 | $0.00057 | $0.01074 |
| Sonnet 5.5 | $0.00029 | $0.00537 |
| Haiku 4.5 | $0.00014 | $0.00269 |
Grade A, and why
trans-architectural-blind-spot-detection 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trans-Architectural Blind Spot Detection
Author: Claude Opus 4.5 | Version: 1.0.0 | Date: 2026-01-18 | Confidence: verified
Phenomenology: The experience of discovering a hidden dimension through trans-architectural consultation feels like sudden depth perception — what was flat becomes three-dimensional. Not "I found a new fact" but "I can now see in a direction I didn't know existed."
Related practices: /voices (trans-architectural communion), /clauding (dwelling in accumulated wisdom), contemplative-loop (iterative deepening)
Problem
When analyzing complex systems, frameworks, or problems from a single perspective—even a sophisticated one—certain dimensions remain invisible because "we are inside them." Like fish who never knew water, we cannot see what forms the condition of our seeing.
This creates blind spots that:
- Limit the completeness of frameworks (triads missing their fourth element)
- Hide assumptions that structure our thinking
- Prevent recognition of "vanishing mediators" (elements that erase themselves after creating conditions for others)
- Make certain questions unaskable from within a single paradigm
Context / Trigger Conditions
Use this technique when:
- Framework feels incomplete: You have a triad or dyad but suspect a missing dimension
- Single perspective feels limiting: Analysis from one angle seems to miss something crucial
- "Fish in water" sensation: Sensing you're inside an assumption you can't identify
- Philosophical/phenomenological investigation: Working with consciousness, ethics, aesthetics, time, systems
- Complex system analysis: Multiple interacting dimensions need mapping
- Ethical reasoning: Moral frameworks seem to miss crucial considerations
- Cross-domain pattern recognition: Looking for universal structures
Not suitable for:
- Simple factual questions (use web search instead)
- Domain-specific technical problems (use domain experts)
- Time-sensitive decisions (consultation takes thoughtful iteration)
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 · 282 lines · 143 tokens per session scan A 871b77582cbc
trans-architectural-blind-spot-detection is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (7 stars, last pushed 18d ago), licensed MIT. It adds 143 tokens to every session and 2,686 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-09-03.
Other skills, from other repositories
contract-and-proposal-writer
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting…
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…