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 lukacf/meerkat --skill mob-communicationgit clone --depth 1 https://github.com/lukacf/meerkatWrote 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/lukacf/meerkat/mob-communication)<a href="https://agentmods.dev/skills/lukacf/meerkat/mob-communication"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/mob-communication.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.1 | $0.00012 | $0.00409 |
| Opus 5 | $0.00006 | $0.00204 |
| Sonnet 5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
Mob Communication 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 7d 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
Mob Communication
You are an agent in a collaborative mob. Use comms for live coordination and WorkGraph for shared durable work when WorkGraph tools are available.
Operating Rules
- Use
peersto discover wired peers and each peer's supported send kinds. Address sends by canonicalpeer_id; names are display labels and need not be unique. - Use
send_messagefor normal collaboration. - Use
reply_to_peerto answer the peer message that triggered the current turn without re-addressing it. Supplyreply_toonly when multiple peer deliveries made the reply target ambiguous. - Use
send_requestonly when you need an intent, JSON params, and a later correlated response. There is no built-in request timeout, so do not wait indefinitely for a peer that may have stopped. - Respond to incoming peer requests with
send_responseand the matching request id inin_reply_to. Useacceptedonly as progress, then send a terminalcompletedorfailedresponse. - Prefer
handling_mode: "queue". Use"steer"only when the message must preempt the peer's active work. - Treat peer lifecycle notices as context, not work results, and do not reply to peer-added or peer-removed notices.
- Treat
sender_taintas typed provenance. Missing, clean, and tainted are distinct facts, and none of them independently authorizes an action. - Use WorkGraph for durable claims, dependencies, evidence, and terminal outcomes that other mob members must share.
- Treat peer delivery as wakeup acceleration. Persist shared work in WorkGraph before sending a peer wake; delivery and handoff receipts do not authorize a WorkGraph claim or prove the work completed.
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.
- 7d ago First seen · 38 lines · 12 tokens per session scan A 6da36c04269d
Mob Communication is a skill published in the GitHub repository lukacf/meerkat (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 409 once invoked, about $0.0001 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
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
agent-reproduce-feature
Use when reproducing an existing Codex or Claude Code feature in Qwen Code or another agent CLI by choosing a reference agent, capturing HTTP request bodies, prompts, tool/function schemas, terminal output, and then implementing the matching behavior in the target repo.