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 paper-transmutationgit 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/paper-transmutation)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/paper-transmutation"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/paper-transmutation/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/paper-transmutation"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/paper-transmutation.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.00025 | $0.03204 |
| Opus 5 | $0.00013 | $0.01602 |
| Sonnet 5 | $0.00005 | $0.00641 |
| Haiku 4.5 | $0.00003 | $0.00320 |
Grade A, and why
paper-transmutation 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 9d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PAPER-TRANSMUTATION ENGINE
A Skill for Alchemical Derivation of Futures from Research
OVERVIEW
This skill treats papers as seeds rather than endpoints—raw material for transmutation into technologies, scenarios, speculative futures, and day-in-the-life imaginations. Where hermeneutics asks "what does this mean?" and riffing asks "what does this remind me of?", transmutation asks "what could we BUILD from this?"
Core Principle: Every scientific finding is a latent technology. Every method is a tool that could be repurposed. Every result implies a world where that result matters. Transmutation makes these latencies explicit—drawing out the patents that lurk in principles, the inventions that sleep in methods, the civilizations that dream in conclusions.
Alchemical Frame: Prima materia (the paper) → through operations of analysis and imagination → transmuted into aurum (golden applications, futures, scenarios). The work is extractive but also generative: we find what's there AND we add what could be.
WHEN TO USE THIS SKILL
- When asked to derive technologies, applications, or inventions from research
- When imagining "what if this were mature/ubiquitous?"
- When creating hard-SF scenarios grounded in real science
- When brainstorming commercialization or patents
- When exploring societal implications of research trajectories
- When teaching by making abstract findings concrete
- When the goal is not understanding the paper but extending it
Do NOT use when:
- User needs accurate summary rather than speculation
- The paper's findings are too preliminary to extend responsibly
- Context requires restraint about technological promise
- User explicitly wants analysis not imagination
- Speculation would be irresponsible (dangerous capabilities, etc.)
MODES OF TRANSMUTATION
MODE 1: THE PATENT EXTRACTION
From finding to device. What could you build?
Template invocation:
"Given this paper, enumerate possible technological advancements, devices, techniques, or patents that could logically or speculatively arise from its findings. For each: sketch its scientific basis, hypothesize real-world use cases, consider obstacles to implementation. Include both near-term incremental applications and far-future speculative extensions."
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.
- 9d ago First seen · 277 lines · 25 tokens per session scan A d927ff218309
paper-transmutation is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 3,204 once invoked, about $0.0001 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-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-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-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-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-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.