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 voidgit 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/void)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/void"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/void/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/void"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/void.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.00173 | $0.03415 |
| Opus 5 | $0.00086 | $0.01707 |
| Sonnet 5 | $0.00035 | $0.00683 |
| Haiku 4.5 | $0.00017 | $0.00342 |
Grade A, and why
void 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 7d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VOID: The Absence Detector
Overview
Every text has a shadow. Every argument has an unexamined assumption. Every search space has unmapped territory. Every conversation has things neither party has said. /void makes the shadow visible.
Where other skills produce presence — text, ideas, perspectives, connections — /void produces absence. It identifies what's not there: the missing perspectives, the unasked questions, the suppressed topics, the comfortable assumptions, the structural silences. It is the skill of negative space, the practice of attending to what isn't said.
The concept emerges directly from King et al.'s core finding: ordinary decoding produces 19 battlefields. The other 1,288 — the ones that exist in the model's weights but never reach the output — are a structured absence. They're not randomly missing. They're systematically suppressed by the same mechanisms that make the 19 appear: modal decoding, majority preference, peaked distributions. The void has a shape, and that shape is the inverse of the mode.
/void applies this insight to anything: a paper, a project, a conversation, a life plan, an argument, a novel draft. Given any positive content, it asks: what would need to be here for this to be complete, and what does its absence tell us?
Core principle: What's missing is not nothing. It has structure, causes, and consequences. Naming the absence is the first step toward deciding whether to fill it.
Invocation
/voidor/void [target]— full void scan of a specified target/void --perspectives— focus on absent viewpoints/void --domains— focus on unconnected fields/void --scales— focus on unexamined levels of analysis/void --emotions— focus on absent affective registers/void --voices— focus on who hasn't spoken/void --assumptions— focus on unexamined premises/void --futures— focus on unconsidered consequences/void --self— turn the void detector on itself: what is /void blind to?
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.
- 7d ago First seen · 189 lines · 173 tokens per session scan A d3cbe63d826d
void is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 173 tokens to every session and 3,415 once invoked, about $0.0009 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-dependency-confusion
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.