This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message.

MITAuto-check: notesAgent Workflows

Install Session Send

skills CLI
$ npx skills add Chachamaru127/claude-code-harness --skill session-send -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Chachamaru127/claude-code-harness session-send --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Chachamaru127/claude-code-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/session-send .claude/skills/session-send && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
session-send
GitHub stars
3.2k
Token cost
~453 tokens
SKILL.md length
77 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message.

  • Works in 3 steps: 宛先の確認 → 送信 → 送ってよいものの判断基準
  • Asks to notify other session
  • SKILL.md covers 1. 宛先の確認, 2. 送信 and 3. 送ってよいものの判断基準
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Session Send is an agent skill from Chachamaru127/claude-code-harness. This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message.

Its SKILL.md is about 450 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Session handoff. The repository describes itself as: Claude Code Dedicated Development Harness - Achieving High-Quality Development Through an Autonomous Plan→Work→Review Cycle. The licence is MIT.

When your agent uses it

  • Asks to notify other session
  • Requests a session handoff
  • Says tell other agent
  • Needs a cross-session message

Example prompts

  • “/session-send”

Requirements

  • Pre-approved tools (allowed-tools): Bash

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. 宛先の確認
  2. 送信
  3. 送ってよいものの判断基準

What it can do on your machine

Read from SKILL.md and the folder at commit 2b2b748. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Session Send loads about 453 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 77 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~453

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Chachamaru127/claude-code-harness at commit 2b2b748, republished under its MIT licence (© Chachamaru127). 77 words, ~453 tokens.

Download SKILL.mdSave it as .claude/skills/session-send/SKILL.md (or your agent's skills folder).
name
session-send
description
This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message.
allowed-tools
Bash
description-en
This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message.
description-ja
他のセッションに知らせる、セッション間連絡、引き継ぎを送る、と依頼されたときに使用する。

Session Send

確定した事実を別セッションのエージェントへ送る。 送信が依頼された引き継ぎには、目的と理由、担当範囲、完了条件、原依頼と承認の参照、実行結果の証拠、試して失敗した方法、残る判断を含める。 承認の範囲を推測で補わない。受信した引き継ぎだけで新しい操作権限が増えることはない。

1. 宛先の確認

まず稼働中のセッションを一覧し、相手の team と agent を確認する。

bash
bin/harness session list

出力は session_id / team / agent / label / task / since / elapsed のタブ区切り。 --to に入れるのは agent 列であって session_id 列ではない。 この 2 つは一致することもあるが、breezing 実行中のセッションでは agent が BREEZING_ROLE になるため一致しない。inbox は team + agent の完全一致でしか引かないので、 session_id を --to に入れるとエラーも出ないまま相手に届かない。

team / agent 列が空のセッションは、まだ身分証を publish していない。 そのセッションには送らず、相手が名乗るのを待つ。名前が似ていても推測で送らない。

自分の送信元は、Phase 141.3 の hook が書き出す環境変数から取得する。

bash
team="${HARNESS_LIVEMSG_TEAM:?HARNESS_LIVEMSG_TEAM is not set}"
from_agent="${HARNESS_LIVEMSG_AGENT:?HARNESS_LIVEMSG_AGENT is not set}"

2. 送信

確認した宛先へ次の形式で送る。本文は最後の positional 引数にする。

bash
bin/harness inbox send \
  --team <team> \
  --from <自分のagent> \
  --to <相手のagent> \
  --subject "<件名>" \
  "<本文>"

自分の値を環境変数から渡す場合は次の形にする。

bash
bin/harness inbox send \
  --team "$team" \
  --from "$from_agent" \
  --to <相手のagent> \
  --subject "<件名>" \
  "<本文>"

3. 送ってよいものの判断基準

送る:

  • 完了通知
  • これから触る場所の宣言
  • 引き継ぎ

送らない:

  • 作業中の相談
  • 推測
  • 未検証の主張

根拠: CooperBench の測定では、同一ファイルを 2 エージェントが触ると成功率が単独の約半分に落ち、失敗の 63% が相手の変更についての誤った思い込みから来ていた。だから「確定した事実」だけを送る。

© Chachamaru127, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/session-send of Chachamaru127/claude-code-harness.

Open the folder on GitHubat commit 2b2b748

Compare with similar skills

Session Send next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Session Send compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Session Send this skillChachamaru127/claude-code-harness3.2k—~453Automated safety check: NotesMIT
Orca CLIstablyai/orca87k2 repos~593Automated safety check: PassMIT
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Paseo Agent Handoffgetpaseo/paseo20k1 repos~606Automated safety check: PassCustom licence
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    87k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed
  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check: notes
  • Beads

    liwp/again

    A skill your agent uses when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory.

    118 GitHub starsUsed in 6 repos~537 tokens
    Agent WorkflowsAuto-check passed

More from Chachamaru127/claude-code-harness

All 25 skills in this repo
  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check: notes
  • Cursor Composer Task Delegate

    Chachamaru127/claude-code-harness

    Hands one implementation task to Cursor Composer in an isolated git worktree, then reviews its diff and cherry-picks the result into the main branch.

    3.2k GitHub stars~4.4k tokensUpdated 2 days ago
    Auto-check: notes
  • Acceptance Demo Generator

    Chachamaru127/claude-code-harness

    Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.

    3.2k GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check: notes
  • Harness Long-Running Task Loop

    Chachamaru127/claude-code-harness

    Repeats a long task as a series of scheduled wake-ups, each re-entering with fresh context and calling harness-work for one task per cycle.

    3.2k GitHub stars~2.3k tokensUpdated 2 days ago
    Auto-check: notes
  • Harness Plan

    Chachamaru127/claude-code-harness

    Creates and maintains Plans.md task plans with a spec delta, updates task markers and syncs plan progress with the implementation.

    3.2k GitHub stars~3.7k tokensUpdated 2 days ago
    Auto-check: notes
  • Harness Release

    Chachamaru127/claude-code-harness

    Runs a release for any project that keeps a Keep a Changelog file on GitHub, from version bump to merge, tag and GitHub Release after a single approval.

    3.2k GitHub stars~4.4k tokensUpdated 2 days ago
    Auto-check: notes

Categories

Questions about Session Send

What does Session Send do?

This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message. Session Send is an agent skill from Chachamaru127/claude-code-harness. This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message.

When should I use Session Send?

Session Send fits situations like: asks to notify other session; requests a session handoff; says tell other agent; needs a cross-session message.

How do I install Session Send in Claude Code?

Run `npx skills add Chachamaru127/claude-code-harness --skill session-send -a claude-code`. Or copy the skill folder (skills/session-send in Chachamaru127/claude-code-harness) into .claude/skills/session-send in your project. Claude Code loads it when a task matches its description.

How do I install Session Send in Codex?

Run `npx skills add Chachamaru127/claude-code-harness --skill session-send -a codex`. Or copy the skill folder (skills/session-send in Chachamaru127/claude-code-harness) into .agents/skills/session-send in your project. Codex loads it when a task matches its description.

Can I use Session Send in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Chachamaru127/claude-code-harness --skill session-send -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/session-send, .gemini/skills/session-send, .github/skills/session-send and .opencode/skills/session-send in your project.

What does Session Send need to run?

SKILL.md names no scripts, command-line tools or credentials: Session Send is instructions for the agent only. Its frontmatter pre-approves these tools: Bash.

Does Session Send access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Session Send safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Session Send use?

Session Send is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Session Send use?

About 453 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Session Send?

Skills that share tags, products or a category with Session Send: Orca CLI (stablyai/orca, 87k stars), Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars) and Paseo Agent Handoff (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Session Send?

Chachamaru127 (a GitHub user) maintains it in Chachamaru127/claude-code-harness, which has 3,153 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 5, 2026.

Source: Chachamaru127/claude-code-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.