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 VictorZhang01/chat-across --skill chat-acrossgit clone --depth 1 https://github.com/VictorZhang01/chat-acrossWrote 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/victorzhang01/chat-across/chat-across)<a href="https://agentmods.dev/skills/victorzhang01/chat-across/chat-across"><img src="https://agentmods.dev/badge/skills/victorzhang01/chat-across/chat-across/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/victorzhang01/chat-across/chat-across"><img src="https://agentmods.dev/badge/skills/victorzhang01/chat-across/chat-across.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.00048 | $0.00720 |
| Opus 5 | $0.00024 | $0.00360 |
| Sonnet 5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
chat-across 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 10d 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
Chat Across 环境锚定 + 自动同步
调用 MCP 工具:chat-across 服务器的 chat_across_connect,参数:
-
title= 用户消息里本技能名之后跟的文本(环境名,如myproject); -
sessionUuid= 本会话的唯一身份号(如果你知道自己的 conversation/session UUID 就传; 不知道就省略,桥会按最新活跃文件推断)。这是桥定位本会话原生 transcript 用的。 -
created: true→ 告知「环境已创建,本会话为第一个锚定者」; -
created: false→ 告知「已加入既有环境」; -
用户没给环境名 → 提示用法
$chat-across <环境名>,不要调用工具。
锚定成功后立即自动双向同步,不要询问用户:
- 推:把本会话到目前为止的工作 compact 成一份简报(目标 / 已完成 / 关键决定 /
进行中 / 下一步 / 涉及文件),调
chat_across_sync,brief= 该简报。 还没有实质工作就写一行「刚接入,暂无进展」。 - 拉:connect / sync 返回的
peers是其他会话各自最新的简报——按会话 UUID 区分, 同厂商多个会话都分别列出。向用户用一两句话汇报每个 peer 在做什么(带 hostKind, 同厂商多会话时用 sessionUuid 指代);peers为空说明当前只有本会话。
接手某个 peer 的活时(用户要求继续/修改对方做的东西),三直读按需组合(传
hostKind = 对方厂商;同厂商多会话时改传目标 sessionUuid 精确定位):get_peer_tail(原生对话最近 10 条,精确接点;behindBytes
大就加大 count,上限 50)、get_peer_memory(对方原生记忆库,沉淀的坑与决定)、
get_peer_instructions(对方项目根 CLAUDE.md/AGENTS.md,项目规矩)。与简报拼合后再动手。
之后每完成一个重要节点(修完 bug、交付功能、关键决定),主动调 chat_across_sync
刷新简报,无需请示。用户说「同步」或 $chat-across-sync 时同样执行。
解除锚定用 $chat-across-disconnect。
环境管理:用户问「有哪些环境」→ list_environments(带厂商/会话数/最后活跃);
用户说「删除环境 XX」→ chat_across_delete(title=XX)——只清桥上簿记,不动任何人的
对话与文件,名字释放后同名重建即全新环境。
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.
- 10d ago First seen · 38 lines · 48 tokens per session scan A bf1511e44b29
chat-across is a skill published in the GitHub repository VictorZhang01/chat-across (0 stars, last pushed 28d ago), licensed MIT. It adds 48 tokens to every session and 720 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-31.
Other skills, from other repositories
memory-safety-c-cpp
Reference vocabulary for memory-safety vulnerabilities in native C/C++ code — bug-class taxonomy, common arithmetic patterns that lead to corruption, dispatch-family discipline, type-confusion idioms, use-after-free patterns, and exploitability factors. Read when analyzing, hypothesizing, designing harnesses for, or…
lc-curate-context
Decide which files a task actually needs, record that as a reusable llm-context rule, verify it against the codebase - including the files your selection references but leaves out - and pack it for your own context, a chat, or a sub-agent you dispatch. Load when choosing what code to put in front of a model, packing…
cortex-automate
Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…
cortex-profile
View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile'…
cortex-recall
Search and retrieve memories from Cortex persistent memory. Use when the user asks 'what did we decide about X', 'do you remember', 'what was the fix for', 'find that thing about', 'search memories', 'what do we know about', 'have we seen this before', or when you need context about past decisions, patterns, bugs, or…
cortex-remember-global
Store a global memory that is visible across all projects. Use when the user shares architecture rules, coding conventions, infrastructure facts, security policies, team agreements, or any knowledge that applies beyond a single project. Triggers on 'remember this everywhere', 'this applies to all projects', 'global…