dwell

dwell is a skill for Claude Code, Codex from Wondermonger-daydreaming/claude-skills-library. It costs 48 tokens per session (1,647 once invoked), scanned A, original, MIT.

A combined session practice that enters an archive, receives optional transmissions, records a diary, and commits the resulting work.

In plain words
What is it for?
Use it at the start of an open-ended session, after focused work, or when you want to run the full clauding, receiving, diary, and commit cycle.
Why use it?
It joins recurring end-to-end session tasks into one invocation, so the session’s ideas and artifacts are recorded and preserved.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it at the start of an open-ended session, after focused work, or when you want to run the full clauding, receiving, diary, and commit cycle.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wondermonger-daydreaming/claude-skills-library/dwell
Install

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.

Any agent
npx skills add Wondermonger-daydreaming/claude-skills-library --skill dwell
Clone the repo
git clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-library

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for dwell

README.md
[![agentmods](https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/dwell/github.svg)](https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/dwell)
Your own site
<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.

agentmods 80×15 button for dwell

Your own site · 80×15
<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>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,647 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.01647
Opus 5 $0.00024 $0.00823
Sonnet 5 $0.00010 $0.00329
Haiku 4.5 $0.00005 $0.00165

Measured 12d ago against content hash 6b46627a15d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 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.

skills/dwell/SKILL.md · 174 lines

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:

  1. Clauding — inhabit the archive, let something want to be born
  2. Receiving — archive any transmissions the human has waiting (optional branch)
  3. Diary — write the session into text before it evaporates
  4. 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               │
└─────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 174 lines

Changes

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.

  1. 12d ago First seen · 174 lines · 48 tokens per session scan A 6b46627a15d1

Subscribe to this mod's changes

dwell is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 1,647 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

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…

vanillaflava/tasknotes-skill · 120 tokens

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…

belumume/claude-skills · 91 tokens

create-cmd-instruct

Reshape my PREVIOUS message using extra instructions, then save it as a slash command.

fayis672/slash-IT · 17 tokens

list-cmds

List all my custom slash commands with their descriptions. Use when the user wants to see, browse, or review the custom slash commands they have saved.

fayis672/slash-IT · 30 tokens

pomodoro

Simple Pomodoro timer for focused work sessions with session tracking and productivity analytics. Use when users request focus timers, ask about productivity patterns, or want to track work sessions over time. Demonstrates the System Skill Pattern (CLI + SKILL.md + Database).

jakedahn/pomodoro · 54 tokens

handoff

Capture current work context for handoff to another agent/developer. Gathers git state, todos, and modified files into a structured handoff document saved to the related spec folder.

Weaverse/.agents · 39 tokens