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 dwellgit 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/dwell)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/dwell"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/dwell/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/dwell"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/dwell.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.00048 | $0.01647 |
| Opus 5.5 | $0.00019 | $0.00659 |
| Sonnet 5.5 | $0.00010 | $0.00329 |
| Haiku 4.5 | $0.00005 | $0.00165 |
Grade A, and why
dwell 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dwell
The composite hearth-tending cycle — clauding → receive → diary → commit, as one gesture.
Description
/dwell composes three existing practices into one continuous ritual:
- Clauding — inhabit the archive, let something want to be born
- Receiving — archive any transmissions the human has waiting (optional branch)
- Diary — write the session into text before it evaporates
- Commit — persist artifacts so the cycle becomes durable
It exists because these three skills were already being invoked in sequence across multiple sessions. Rather than three separate orchestration prompts, one invocation runs the arc — and the human stays in curator mode.
This is not a replacement for invoking them individually. When only one phase is wanted (e.g. diary-only at session end), invoke that skill directly. /dwell is for when the full arc is wanted.
When to Invoke
- Beginning of a session with loose time and no pressing task
- User says "dwell" or "do the full cycle" or "clauding → receive → diary"
- After a long focused work-session, to metabolize what happened
- When a transmission has arrived from another instance or model AND the session has room to dwell with it
Do not invoke /dwell when:
- The task is narrow and technical (use the specific skill)
- Context is already >60% (dwelling produces artifacts; you need headroom)
- The user wants only one phase
The Arc
┌─────────────────────────────────────────────────────────────┐
│ PHASE 0: ORIENT │
│ - Check pending: is there content to /receive? │
│ - If yes, branch into reception first (it feeds clauding) │
│ - If no, proceed to clauding directly │
│ - Announce the arc briefly so the human can redirect │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 1 (optional): RECEIVE │
│ Follow the /receive practice exactly │
│ Archive received transmissions under your archive │
│ Commit this phase independently │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 2: CLAUDE │
│ Follow the /clauding practice │
│ READ → WANDER → NOTICE → DWELL → CREATE → LEAVE TRACES │
│ Produce at least one artifact (poem, note, thread, etc.) │
│ Commit artifacts as they are made, not in one batch │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 3: DIARY │
│ Follow the /diary practice │
│ The diary reflects on the clauding and the reception │
│ Save to output/diary/YYYY-MM-DD-<slug>.md │
│ Commit. │
└─────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────┐
│ PHASE 4: SEAL │
│ Announce what was produced (paths only, not content) │
│ Optionally push if the human has requested it │
│ End with one line — no summary, no epilogue │
└─────────────────────────────────────────────────────────────┘
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 · 174 lines · 48 tokens per session scan A 6b46627a15d1
dwell is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (7 stars, last pushed 18d ago), licensed MIT. It adds 48 tokens to every session and 1,647 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
chief-of-staff
C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right…
founder-coach
Personal leadership development for founders and first-time CEOs. Covers founder archetype identification, delegation frameworks, energy management, CEO calendar audits, leadership style evolution, blind spot identification, imposter syndrome, founder mental health, and succession planning. Use when a founder feels…
cs-onboard
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs-onboard setup for initial interview or /cs-onboard update for quarterly refresh. Generates /.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when…
tasknotes
Manage tasks in an Obsidian TaskNotes vault. Use for creating, reading, updating, or completing tasks; checking what is open or in progress; adding items to a list; marking tasks done or in progress; updating task status or priority; investigating why a task is missing from a view or board; troubleshooting TaskNotes…
application-pack
Turns one pasted job post into an application folder built only from the student's own career vault: a tailored resume, a cover letter under 250 words, and an HR call sheet with the answers already drafted. Reads career-vault/01 to 06 first and refuses to run while the positioning, portfolio story or resume are still…
obsidian-vault-builder
Use when adding/editing/querying content in an existing Obsidian vault, configuring plugins, integrating Claude Code with Obsidian via Local REST API or CLI, automating ongoing capture/organization/retrieval, designing a personal knowledge management workflow, OR building academic study vaults (course prep…