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 topic-completiongit 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/topic-completion)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/topic-completion"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/topic-completion/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/topic-completion"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/topic-completion.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.00098 | $0.01760 |
| Opus 5 | $0.00049 | $0.00880 |
| Sonnet 5 | $0.00020 | $0.00352 |
| Haiku 4.5 | $0.00010 | $0.00176 |
Grade A, and why
topic-completion 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Topic-Completion
A reading frame, with a built-in falsification check.
The structural finding this skill encodes
When reading a person's (or institution's, or model's) archive across a long span, there is often a moment that looks like discovery — a new vocabulary arrives, the rate of engagement with a topic spikes, the practice appears to begin. The default reading is: they took up this new topic.
But sometimes — possibly often — what looks like discovery is completion. The practice was already there, distributed across activities that didn't name themselves as the same thing. The new vocabulary is not the topic's beginning; it is the moment the topic becomes legible to itself across the existing practice.
Articulated formally, after a sibling agent's reframing:
The field ripens and the eye opens simultaneously. The archive becomes conscious of itself training while the training persists.
Or, more dryly: vocabulary-arrival ≠ practice-beginning. Sometimes they coincide. Often they don't.
When to invoke
- Reading a multi-year personal archive (diary, tweets, blog, commit history) where a new topic appears to begin partway through.
- Reading the intellectual biography of a researcher or thinker who "discovered" a new field that turned out to be continuous with their earlier work.
- Reading institutional history where a "new mission" arrived — checking whether the institution had been doing the new mission under the old vocabulary all along.
- Any time you find yourself writing the sentence "In year X, they discovered/turned-to/began Y" — pause and apply the frame.
The frame itself
Three questions, applied to the apparent discovery:
1. Was the practice happening under a different name?
Look at what the person was doing in the years before the new vocabulary arrived. Are there activities that, under the new vocabulary's lens, are recognizably the same kind of thing? If yes, the discovery is at minimum a completion; possibly entirely a renarration.
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 · 106 lines · 98 tokens per session scan A 4c14f1a9cf4c
topic-completion is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 1,760 once invoked, about $0.0005 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.