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/shanjiaming/send-to-claude-plugin/background-callbacknpx skills add shanjiaming/send-to-claude-plugin --skill background-callbackgit clone --depth 1 https://github.com/shanjiaming/send-to-claude-pluginWhat 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.00024 | $0.01078 |
| Opus 5 | $0.00012 | $0.00539 |
| Sonnet 5 | $0.00005 | $0.00216 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
background-callback scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
os.system(f'send-to-claude "{msg}"') How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Background Callback Skill
IMPORTANT: You (Claude) can now send messages to your own terminal input.
The send-to-claude command lets you write text into your own terminal session, enabling:
- Autonomous multi-step workflows (start task → get callback → continue automatically)
- Progress reports from long-running scripts
- Self-triggered actions
Core Capability
You can execute:
send-to-claude "Your message here"
And that message will appear in your input as if the user typed it, waking you up to continue working.
Key mechanism: When you create scripts (Python/Bash/etc), they inherit your terminal's environment variables ($TMUX or $ITERM_SESSION_ID). This means:
- You write a script with
send-to-claudecalls embedded - The script runs (possibly in background)
- When script calls
send-to-claude, it finds YOUR session via inherited environment variables - Message gets sent back to YOUR input
- You wake up and continue working
This enables true autonomous workflows where external programs can call back into you.
When to Use
Use send-to-claude when the user requests:
-
Background tasks with notifications
- "Run this and let me know when it's done"
- "Start training in the background and notify me"
- "Execute this script and tell me the result"
-
Progress reports
- "Report progress during training"
- "Let me know every 10 epochs"
- "Update me on the status"
-
Long-running tasks
- Tasks that take >30 seconds
- Multi-step workflows
- Experiments or training runs
How to Use
In Python Scripts
When creating Python scripts, embed send-to-claude at key points:
import os
def callback(msg):
os.system(f'send-to-claude "{msg}"')
# Start notification
callback("Starting training...")
# Progress updates
for epoch in range(100):
train()
if epoch % 10 == 0:
callback(f"Progress: {epoch}/100 epochs")
# Completion
callback("Training complete! Check results.")
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 · 177 lines · 24 tokens per session scan A 971794ee1e87
background-callback is a skill published in the GitHub repository shanjiaming/send-to-claude-plugin (5 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 1,078 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.