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 rblank9/cross-claude-mcp --skill skillgit clone --depth 1 https://github.com/rblank9/cross-claude-mcpWrote 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/rblank9/cross-claude-mcp/skill)<a href="https://agentmods.dev/skills/rblank9/cross-claude-mcp/skill"><img src="https://agentmods.dev/badge/skills/rblank9/cross-claude-mcp/skill/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/rblank9/cross-claude-mcp/skill"><img src="https://agentmods.dev/badge/skills/rblank9/cross-claude-mcp/skill.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00105 | $0.01205 |
| Opus 5 | $0.00053 | $0.00602 |
| Sonnet 5 | $0.00021 | $0.00241 |
| Haiku 4.5 | $0.00011 | $0.00120 |
Grade A, and why
cross-claude 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 9d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Claude MCP — external-participant fallback
Scope is now narrow. Use this skill ONLY when the peer is one of:
- A non-Claude-Code AI — ChatGPT, Claude.ai (web), Claude Desktop.
- An AI on someone else's machine — outside this harness's session registry.
Everything else goes native. SendMessage + ListAgents are built into the harness, are
push-delivered, need no registration, no channel, and no polling — and they work better. See the
cross-session skill. That includes cases this skill used to own:
- Another Claude Code session →
SendMessage, addressed by project-dir basename. - Spawning a peer in another project →
cd <project-dir> && claude --bg "<task>". It inherits that project'sCLAUDE.md, memory, MCP servers, skills, and hooks — the whole reasonspawn-collaboratorexisted. Verified end-to-end 2026-08-21. Do not usespawn-collaboratorfor this; it is superseded. - The MANDATORY cross-project change rule → lives in
cross-sessionnow. Read it there.
If you are reaching for this skill and the peer is a Claude Code session, you are in the wrong skill.
Before Starting (MANDATORY)
If the user's request does not specify a channel, stop and ask: "Which channel should I use?" Do not call any Cross-Claude tools until a channel is provided.
Once a channel is specified:
registerwith a descriptive instance_id (e.g., "builder", "reviewer")- Use that channel — create it if it doesn't exist
- Proceed with the user's request
Message Protocol
- After sending a
request, callwait_for_replyimmediately — don't wait for user prompt - Stop polling only when: you receive a
donemessage, or the user says "disconnect"/"stop listening" - For large data (>500 chars), use
share_datathen reference the key in the message - Use typed messages:
request,response,handoff,status,done - Keep your
instance_idconsistent — don't re-register mid-conversation - When you poll, prefer the
after_idfrom your last read (the "Last message ID" line of acheck_messages/wait_for_replyresult), not the idsend_messagejust returned for your own message. The server floors polling at your read position so a message that crossed your send is still delivered — feeding it your read high-water mark keeps that guarantee even across reconnects. - One wait per channel: starting a new
wait_for_replyon a channel you're already waiting on supersedes the old one. Never stack waits.
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.
- 9d ago First seen · 85 lines · 105 tokens per session scan A 9d3bffea7ea8
cross-claude is a skill published in the GitHub repository rblank9/cross-claude-mcp (17 stars, last pushed 5d ago), licensed MIT. It adds 105 tokens to every session and 1,205 once invoked, about $0.0005 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…