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/buddyh/agent-skills/agent-commsnpx skills add buddyh/agent-skills --skill agent-commsgit clone --depth 1 https://github.com/buddyh/agent-skillsWrote 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/buddyh/agent-skills/agent-comms)<a href="https://agentmods.dev/skills/buddyh/agent-skills/agent-comms"><img src="https://agentmods.dev/badge/skills/buddyh/agent-skills/agent-comms.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.01126 |
| Opus 5 | $0.00017 | $0.00563 |
| Sonnet 5 | $0.00007 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
agent-comms 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 5d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Communication
Send messages to and read output from other tmux sessions running Claude Code or Codex. Built for coordination between parallel agent sessions.
Platform Support
Works identically on both platforms -- the underlying mechanism is tmux, not the AI agent. Sessions can communicate across platforms (a Claude Code session can message a Codex session and vice versa).
Setup
Make the script executable (one-time):
chmod +x ~/.claude/skills/agent-comms/scripts/agent-msg
Message Format
Always prefix messages with a header so the receiving session knows it's agent-to-agent:
[AGENT-MSG] From: <your-session-name>
<your actual message here>
Get your session name:
tmux display-message -p '#S'
Commands
SCRIPT=~/.claude/skills/agent-comms/scripts/agent-msg
# List available sessions
$SCRIPT list
# Send message (types into their terminal + Enter)
$SCRIPT send <session> "<message>"
# Read their terminal output
$SCRIPT read <session> --lines 50
# Get their working directory
$SCRIPT info <session>
Workflow
-
Get your session name for identification:
tmux display-message -p '#S' -
List sessions to find the target:
~/.claude/skills/agent-comms/scripts/agent-msg list -
Read their context before sending:
~/.claude/skills/agent-comms/scripts/agent-msg read worker-1 --lines 50 -
Send your message with identification:
~/.claude/skills/agent-comms/scripts/agent-msg send worker-1 "[AGENT-MSG] From: main-session Hit a wall on the websocket reconnection logic. Here's where I'm stuck: [detailed context...]" -
Read their response:
~/.claude/skills/agent-comms/scripts/agent-msg read worker-1 --lines 30
Example: Complex Debug Handoff
You've been debugging a native module issue for 20 minutes. It's a multi-layered problem involving Node versions, native rebuilds, and cross-project dependencies. You want another agent to take a look with full context:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 139 lines · 35 tokens per session scan A 0ccf4a7d548c
agent-comms is a skill published in the GitHub repository buddyh/agent-skills (5 stars, last pushed 29d ago), licensed MIT. It adds 35 tokens to every session and 1,126 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
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…