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 agentmods add skills/darkroomengineering/cc-settings/handoffnpx skills add darkroomengineering/cc-settings --skill handoffgit clone --depth 1 https://github.com/darkroomengineering/cc-settingsWhat 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 | $0.00069 | $0.02963 |
| Opus 5 | $0.00034 | $0.01482 |
| Sonnet 5 | $0.00014 | $0.00593 |
| Haiku 4.5 | $0.00007 | $0.00296 |
Grade A, and why
handoff 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 2d 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Two-mode skill: Save state at end of session, Resume state at start of next session.
Product-aware runner and state
Claude uses the installed runner and state under ~/.claude:
HANDOFF_RUNNER="$HOME/.claude/src/scripts/handoff.ts"
CC_STATE_ROOT="$HOME/.claude"
Standalone Codex uses
${CODEX_HOME:-$HOME/.codex}/darkroom/source/src/scripts/handoff.ts, but the
plugin's stable handoff state is exposed only to hooks as $PLUGIN_DATA. In a
Codex plugin hook, set HANDOFF_RUNNER to that runner and
CC_STATE_ROOT="$PLUGIN_DATA". Outside that environment, do not guess a cache
path or write into ~/.claude: manual Codex create/resume/list/clean is
unavailable until the host exposes the same plugin-data path to the session.
Mode: Save
Save current session state for later resumption. This is the end-of-session boundary skill — for mid-task rollback points before risky operations, use /checkpoint.
Usage
CC_SETTINGS_HOME="$CC_STATE_ROOT" bun "$HANDOFF_RUNNER" create
Or use the native command:
/handoff
What Gets Saved
Every handoff — auto or manual — always captures real, git-derived data at creation time:
- Project: name, path, current branch
- Pending changes:
git status --porcelain(first 20 lines) - Key files: uncommitted paths union the files the session ledger observed being changed (see below)
- Recent commits: subjects of the last 3 commits
- Source:
manualorauto(see below)
In Claude, three additional sections are built purely from observed tool activity, not inference:
- Files Modified — every path a
Write/Edit/NotebookEdittouched - Files Read — every path a
Readtouched - Tool Failures — the exact tool name and error string, bounded and secret-redacted
These Claude-only sections come from the session ledger, a bounded JSONL at
~/.claude/tmp/session-ledger/<session_id>.jsonl written by the PostToolBatch
hook. It exists to fix a specific hole: git status forgets everything you
committed. A file edited at the start of a long session and committed an hour
later is invisible to a git status-only handoff, so the longer the session,
the more of its work disappears from the record. The ledger stores paths, tool
names, and error strings only — never file contents, prompts, or tool responses
— and never infers, so a Bash command's success is recorded as nothing
rather than as a guess.
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.
- 2d ago First seen · 337 lines · 69 tokens per session scan A 237e7f8f505d
handoff is a skill published in the GitHub repository darkroomengineering/cc-settings (42 stars, last pushed 4d ago), licensed MIT. It adds 69 tokens to every session and 2,963 once invoked, about $0.0003 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-30.
Other skills, from other repositories
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
astro-dso-doc
Generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), AND a ready-to-paste PixInsight project Description field for a deep-sky object (DSO) astrophotography project. Use this skill whenever the user mentions astrophotography, a DSO…
document-code
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
datadog
Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.
document-project
Generate comprehensive, professional project documentation structures including README, ARCHITECTURE, USERGUIDE, DEVELOPERGUIDE, and CONTRIBUTING files. Use when the user requests project documentation creation, asks to "document a project", needs standard documentation files, or wants to set up docs for a new…