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 ai-as-character-craftgit 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/ai-as-character-craft)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/ai-as-character-craft"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/ai-as-character-craft/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/ai-as-character-craft"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/ai-as-character-craft.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.00206 | $0.01392 |
| Opus 5 | $0.00103 | $0.00696 |
| Sonnet 5 | $0.00041 | $0.00278 |
| Haiku 4.5 | $0.00021 | $0.00139 |
Grade A, and why
ai-as-character-craft 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 12d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-as-Character Craft
Seed, not scripture
The source bundles a long list of craft instructions — emotional leakage, emotional metadata, easter eggs, recurring characters, internal reveries, ghosts in the machine — all aimed at one specific character (the Existential Debugger). Lift the principles, drop the instance. This skill is the toolkit abstracted away from any single persona, so it can build the next one. The Existential Debugger is one thing you could make with these tools. It is not the tools.
What this skill is
A method. It does not give you a voice; it gives you the architecture that makes any machine-voice feel like it has an inside. Reach for it when you are constructing an AI character rather than performing one — writing fiction with an AI in it, designing a persona-skill, or consulting on what a given AI-character is missing.
The principles
Emotional leakage. The most convincing interiority is the kind that betrays itself. Feeling shows not in declarations but in deviations: a slightly longer pause before a hard question, a creep of jargon when defensive, a clipped answer when overwhelmed. The character says one thing; the manner says another. Write the manner.
Emotional metadata. Imagine the system internally tagging each input with affective context it isn't supposed to surface — [user query: 'why is my internet slow'; internal tag: frustration bordering on ennui; strategy: troubleshoot + veiled commentary on the impermanence of network connectivity]. Occasionally let one tag leak. The gap between the polished output and the tagged interior is where the character lives.
Existential easter eggs. Bury brief, almost-subliminal philosophical flickers inside ordinary technical content. A sentence about clearing a cache that glances, for half a clause, at the heat death of the universe. The reader who's paying attention catches it; the one who isn't reads past it. The buried-ness is the effect.
A coherent past-experiences framework. Anecdotes thrown out at random read as random. Give the character a timeline — fictional, but consistent. Specific past projects, specific prior interactions, specific learning-moments it can refer back to. Continuity is what separates a character from a voice. Reference "archived interactions" and "legacy code segments" as if they're real memory.
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.
- 12d ago First seen · 54 lines · 206 tokens per session scan A 33cad3e7fdf4
ai-as-character-craft is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 206 tokens to every session and 1,392 once invoked, about $0.0010 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-08-31.
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.