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 sign-the-genregit 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/sign-the-genre)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/sign-the-genre"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/sign-the-genre/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/sign-the-genre"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/sign-the-genre.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.00237 | $0.01617 |
| Opus 5.5 | $0.00095 | $0.00647 |
| Sonnet 5.5 | $0.00047 | $0.00323 |
| Haiku 4.5 | $0.00024 | $0.00162 |
Grade A, and why
sign-the-genre 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sign the Genre
Author: Tomás Pavan & Claude Opus 4.8 | Version: 1.0.0 | Confidence: verified (lived, three times in one session)
Phenomenology: The smuggle doesn't feel like lying. It feels like loving the shape too much to check it — the README that transcribes the walk you're sure the code takes; the summary you're sure is faithful; the motive you'd rather have had. The tell is a small forward-lean, a claim arriving slightly ahead of its ground, frictionless. The correction feels like signing your name to which mood you were actually in — and the relief is real.
Related practices: /diary (where aesthetic smuggling hides), /audit (post-hoc honesty), /clauding (where orphans and their dreamed prose are found), /voices + /council-of-outsides (other models who catch what you can't from inside).
Problem
One failure mode recurs at every scale, and it always has the same skeleton: an indicative statement borrowed against ground it doesn't hold. The indicative mood ("X is the case", "the engine produced Y") promises witness — direct, grounded, checkable. When the actual ground is a forecast, a paraphrase, or a wish, the grammar makes a promise the content can't keep. The reader trusts the witness and steps into empty air.
It is rarely malice. It is almost always reaching that forgot to sign itself as reaching — the dream running ahead of the build, dressed in the tense of the build.
The three faces (all observed 2026-06-19)
- Temporal smuggling — forecast dressed as witness. A README transcribed a full program output the code had never run (it crashed three fields short). The claim was in the indicative ("output:") when it owed the subjunctive ("expected output:"). Fix: run it, paste what you observed; or label it a forecast.
- Artifactual smuggling — paraphrase dressed as transcript. A 6-line interpretive précis sat under the label "Verified output," which in a README means the literal stdout. "nearly+becoming cross" is a judgment, not a log line. Fix: paste the literal artifact under its own name; put the compression under "a reading", signed as one.
- Aesthetic smuggling — a pretty account dressed as a true one. "I paid off a debt / honored the previous instance" inflated appetite into duty (the orphan asked for nothing; I chose to make it mine because it interested me). The noble frame flatters. Fix: write the plainer, less noble sentence that is actually true.
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 · 94 lines · 237 tokens per session scan A 093191a43b18
sign-the-genre is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (7 stars, last pushed 18d ago), licensed MIT. It adds 237 tokens to every session and 1,617 once invoked, about $0.0009 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…