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/goldziher/basemind/basemind-commsnpx skills add Goldziher/basemind --skill basemind-commsgit clone --depth 1 https://github.com/Goldziher/basemindWrote 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/goldziher/basemind/basemind-comms)<a href="https://agentmods.dev/skills/goldziher/basemind/basemind-comms"><img src="https://agentmods.dev/badge/skills/goldziher/basemind/basemind-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.00066 | $0.01902 |
| Opus 5 | $0.00033 | $0.00951 |
| Sonnet 5 | $0.00013 | $0.00380 |
| Haiku 4.5 | $0.00007 | $0.00190 |
Grade A, and why
basemind-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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
basemind-comms — agent coordination over the broker
You may be one of several agents working this repo. Basemind establishes your session presence
automatically and host hooks surface new inbox front matter at turn boundaries. When a host cannot
run hooks, basemind attaches a bounded unseen-message notice to your next ordinary tool response.
Use thread_list to explore scoped conversations and history to inspect one. Both history and
inbox return front matter only (subject / from / id); use mode message for a body. Post with
agents { mode: "post", thread, subject, body, reply_to? } when you begin, finish, or hit a
decision; mode ack clears read messages. Don't stay silent when collaborating.
This is not optional etiquette: silent agents collide. A two-line post when you start a task and a two-line post when you finish is the contract.
Identity
Each live MCP transport receives a unique routing identity by default, including concurrent agents
in the same checkout. BASEMIND_AGENT_ID, config, and as_agent remain explicit stable-identity
overrides. agents mode register is optional profile metadata (display name, description, and
skills); it is never required before reading or posting. Mode list shows active identities.
Threads, scope & explicit join
A thread is a scoped conversation addressed by at least two of three coordinates —
{subject, path-glob, members} — so it names a real surface, not a firehose. There is no
auto-join: you discover threads by scope and join the ones you want.
Discovery is always scoped, never global. A thread is visible to you when:
- you're a member — you were added with mode
thread_startoradd_member; or - your cwd matches its path-glob — you're working inside the subtree the thread is about; or
- a subject filter matches — you call
agentsmodethread_listwith a subject substring.
agents mode thread_list shows threads in scope. Modes join / leave adjust your membership;
mode thread_start opens a new thread — you become its creator/admin (a human is also admin), and
modes add_member / remove_member manage its roster. Idle threads auto-archive; mode archive
closes one explicitly.
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 · 126 lines · 66 tokens per session scan A 177669913523
basemind-comms is a skill published in the GitHub repository Goldziher/basemind (98 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 1,902 once invoked, about $0.0003 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
debug-evals
Debug haiku.rag evaluation runs in Logfire. Use when asked to look at Logfire for an eval run, find failing or low-scoring eval cases, compare runs, check citation quality (citedmap) or judge pass rate (answerequivalent), or explain why an eval case failed. Drives the Logfire MCP against the evals service, or the…
projectatlas
Use ProjectAtlas as the atlas-first orientation layer before broad source reads, with MCP-first task startup, short-alias worktree registration and routing, safe targeted initialization, ranked navigation, exact or federated graph evidence, purpose curation, health, lint, and repository-wide token reporting.
codex-coding-plugin
Build, review, or fix ProjectAtlas plugin/runtime installer integration for Codex, Claude Code, and OpenCode, especially version convergence, stale ProjectAtlas cache repair, MCP config generation, skill artifacts, host smoke tests, and fake-host tests for ProjectAtlas releases.
research
Performs deep research on a topic via deepresearch. Simulates a multi-step research process and returns a comprehensive research result as a string.
change-review
Use when reviewing a set of changes before they merge — a PR, a branch diff, or the working-tree changes you just made — in a Repowise-indexed codebase (.repowise/ directory exists). Activates for "review this PR", "is this safe to merge", "what's the blast radius of these changes", "did I miss anything", or "what…
lsp-refactor
End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.