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/hamchowderr/braynee/commsnpx skills add hamchowderr/braynee --skill commsgit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00080 | $0.01062 |
| Opus 5 | $0.00040 | $0.00531 |
| Sonnet 5 | $0.00016 | $0.00212 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
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 yesterday.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comms Skill
Pulls messages from each client's configured channels (email, Slack), groups them into threads,
summarises every thread with claude -p, and writes one weekly rollup file plus a per-thread
detail file per client into 2. Areas/Comms/<Client>/YYYY-MM/Wn.md.
The data model lives entirely on existing vault notes:
- Client note (
2. Areas/Business/*/Clients/<Client>/<file>.md) declares its channel sources via asources:frontmatter block (slack_channel,slack_workspace_id,email_domains). - Contact notes (
2. Areas/Contacts/<Person>.md) carry a unifiedchannels:array; each entry has akind:(slack, email, linkedin, phone, ...). The skill matches inbound message senders against these to attribute messages to a person.
Nothing about specific clients, channels, domains, or contact identifiers is hard-coded — everything
is discovered from the user's own vault at runtime. A Slack-only client works the same way as an
email-only client; the skill just iterates whatever the client's sources: declares.
Commands
# Sync the current week for one client (client name matches a folder under
# 2. Areas/Business/<Business>/Clients/)
python3 {baseDir}/scripts/comms.py sync "<ClientName>"
# Sync a specific week (Wn = ordinal Monday of the month)
python3 {baseDir}/scripts/comms.py sync "<ClientName>" --week 2026-05-W3
# Backfill every week since a given date (inclusive)
python3 {baseDir}/scripts/comms.py backfill "<ClientName>" --since 2026-03-16
# List all clients with their declared sources + contact counts
python3 {baseDir}/scripts/comms.py list
# Show contacts (and the channels each carries) for one client
python3 {baseDir}/scripts/comms.py contacts "<ClientName>"
Output shape
2. Areas/Comms/<Client Name>/
YYYY-MM/
Wn.md ← weekly rollup, per-thread summaries + Week roll-up footer
threads/
YYYY-MM-DD-<slug>.md ← raw thread detail (one file per thread)
Wn is the ordinal Monday of the month (W1 = first Monday of that month). A week spans
Monday → Sunday and is filed under the month containing its Monday.
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.
- yesterday First seen · 92 lines · 80 tokens per session scan A ba8364307fe4
comms is a skill published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 5d ago), licensed MIT. It adds 80 tokens to every session and 1,062 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…