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/chachamaru127/claude-code-harness/session-sendnpx skills add Chachamaru127/claude-code-harness --skill session-sendgit clone --depth 1 https://github.com/Chachamaru127/claude-code-harnessWrote 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/chachamaru127/claude-code-harness/session-send)<a href="https://agentmods.dev/skills/chachamaru127/claude-code-harness/session-send"><img src="https://agentmods.dev/badge/skills/chachamaru127/claude-code-harness/session-send.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00757 |
| Opus 5 | $0.00017 | $0.00378 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
session-send 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 3d 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.
What it actually says
Session Send
確定した事実を別セッションのエージェントへ送る。
1. 宛先の確認
まず稼働中のセッションを一覧し、相手の team と agent を確認する。
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 が書き出す環境変数から取得する。
team="${HARNESS_LIVEMSG_TEAM:?HARNESS_LIVEMSG_TEAM is not set}"
from_agent="${HARNESS_LIVEMSG_AGENT:?HARNESS_LIVEMSG_AGENT is not set}"
2. 送信
確認した宛先へ次の形式で送る。本文は最後の positional 引数にする。
bin/harness inbox send \
--team <team> \
--from <自分のagent> \
--to <相手のagent> \
--subject "<件名>" \
"<本文>"
自分の値を環境変数から渡す場合は次の形にする。
bin/harness inbox send \
--team "$team" \
--from "$from_agent" \
--to <相手のagent> \
--subject "<件名>" \
"<本文>"
3. 送ってよいものの判断基準
送る:
- 完了通知
- これから触る場所の宣言
- 引き継ぎ
送らない:
- 作業中の相談
- 推測
- 未検証の主張
根拠: CooperBench の測定では、同一ファイルを 2 エージェントが触ると成功率が単独の約半分に落ち、失敗の 63% が相手の変更についての誤った思い込みから来ていた。だから「確定した事実」だけを送る。
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.
- 3d ago First seen · 76 lines · 35 tokens per session scan A afd326bb34a2
session-send is a skill published in the GitHub repository Chachamaru127/claude-code-harness (3,081 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 757 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…