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-to-lived-worldgit 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-to-lived-world)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/paper-to-lived-world"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/paper-to-lived-world/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-to-lived-world"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/paper-to-lived-world.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.00027 | $0.04548 |
| Opus 5 | $0.00014 | $0.02274 |
| Sonnet 5 | $0.00005 | $0.00910 |
| Haiku 4.5 | $0.00003 | $0.00455 |
Grade A, and why
paper-to-lived-world 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PAPER-TO-LIVED-WORLD ENGINE
A Skill for Phenomenological World-Building from Research
OVERVIEW
Every scientific paper implies a world. Not just technologies—worlds. Ways of waking, working, loving, dying. This skill makes those worlds viscerally present through day-in-the-life scenarios: speculative vignettes that show how research findings, when mature and widespread, transform the texture of ordinary experience.
Core Principle: The interesting question isn't "what could we build?" but "what would Tuesday feel like?" Abstract findings become real when you can smell the coffee, feel the weight of the new device, navigate the awkward social dynamics of a changed world. The day-in-the-life form grounds speculation in phenomenology—the lived experience of being a body in a transformed environment.
Why this matters: Futures become real through details. A paper about brain-computer interfaces becomes tangible when you describe the specific headache a character gets at 3pm, the way their partner knows they're "composing" by a slight unfocusing of the eyes, the new etiquette around "silent conversations" at dinner parties. The mundane is where transformation actually lives.
WHEN TO USE THIS SKILL
- When asked to imagine "a day in the life" with mature technology
- When making abstract findings concrete through lived experience
- When generating hard-SF vignettes grounded in specific research
- When exploring social/psychological/cultural implications through narrative
- When teaching by showing rather than telling what a future feels like
- When the goal is empathy with possible futures, not just understanding them
Do NOT use when:
- User needs technical analysis rather than imaginative projection
- The paper's findings are too preliminary to extrapolate responsibly
- Speculation would be misleading about actual research implications
- User explicitly wants non-narrative engagement
- The technology has obvious dual-use concerns that shouldn't be normalized
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 · 353 lines · 27 tokens per session scan A 7c4e0c522c96
paper-to-lived-world is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 4,548 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.