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 darkroomengineering/cc-settings --skill handoffgit clone --depth 1 https://github.com/darkroomengineering/cc-settingsWrote 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/darkroomengineering/cc-settings/handoff)<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/handoff"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/handoff/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/darkroomengineering/cc-settings/handoff"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 26 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00047 | $0.03043 |
| Opus 5.5 | $0.00019 | $0.01217 |
| Sonnet 5.5 | $0.00009 | $0.00609 |
| Haiku 4.5 | $0.00005 | $0.00304 |
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 today.
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 — 338 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, commit or use Claude Code's built-in /rewind.
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.
- today Changed 6ade2c5ed03d
- 4d ago Changed · +1 lines ff65d8f08425
- 18d ago Changed d3af92d89fb2
- 1mo ago Changed · -22 tokens per session 5c83fec29287
- 1mo ago First seen · 337 lines · 69 tokens per session scan A 237e7f8f505d
handoff is a skill published in the GitHub repository darkroomengineering/cc-settings (52 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 3,043 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-30.
Other skills, from other repositories
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
wisdom-forget
Remove a must-keep CocoWisdom entry with rationale. Usage: $wisdom forget --id --rationale " ".
screenpipe-resume-work
Recover the last verified state of an interrupted task and identify the next useful action.
session-search
Use Moraine MCP tools to recover prior agent-session context when the user refers to earlier work, decisions, failures, branches, files, or other agents.
devlog
Keep DEVLOG.md up to date and use it to resume project context in the user's personal developer-log style. Use when the user asks to update, write, continue, summarize, resume, catch up from, or maintain @DEVLOG.md / DEVLOG.md after or before a work session, or asks to capture what they did, learned, decided, got…
lastMonth
Resolve "lastMonth" to a concrete ISO date range relative to your run time — the previous full calendar month. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a task over last month (monthly reports…