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 borghei/Claude-Skills --skill internal-commsgit clone --depth 1 https://github.com/borghei/Claude-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/borghei/claude-skills/internal-comms)<a href="https://agentmods.dev/skills/borghei/claude-skills/internal-comms"><img src="https://agentmods.dev/badge/skills/borghei/claude-skills/internal-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.1 | $0.00049 | $0.02633 |
| Opus 5 | $0.00024 | $0.01316 |
| Sonnet 5 | $0.00010 | $0.00527 |
| Haiku 4.5 | $0.00005 | $0.00263 |
Grade A, and why
internal-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 3d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
10 files 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.
- assets/announcement-template.md 2.0 KB
- assets/comms-plan-template.md 2.8 KB
- assets/sample_announcement.json 882 B
- assets/sample_change.json 840 B
- assets/sample_message_profile.json 208 B
- references/announcement-archetypes.md 8.4 KB
- references/change-comms-cadence.md 10 KB
- scripts/announcement_auditor.py 9.3 KB runs code
- scripts/channel_fit_scorer.py 9.6 KB runs code
- scripts/comms_sequencer.py 10 KB runs code
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.
- 3d ago First seen · 207 lines · 49 tokens per session scan A e9a17e14c10a
internal-comms is a skill published in the GitHub repository borghei/Claude-Skills (714 stars, last pushed 25d ago), with no licence file. It adds 49 tokens to every session and 2,633 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-09-03.
Other skills, from other repositories
shared-monorepo-nx
Nx monorepo build system — workspace configuration, project graph, task pipelines, caching, generators, plugins, and release management.
shared-monorepo-pnpm-workspaces
Skill "shared-monorepo-pnpm-workspaces" from agents-inc/skills, covering pnpm workspaces for monorepo management, critical: before using this skill, philosophy, core patterns and pattern 1: workspace configuration (pnpm-workspace.yaml).
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
run-team-retrospective
Use when a team needs to reflect on a completed period, project, or significant event — to extract what worked, what didn't, and what specific changes to make before the next cycle, rather than repeating the same patterns.
brief-me
Catch the user up from messy workplace context and surface what needs attention.
meeting-to-actions
Turn meeting notes or transcripts into decisions, action items, owners, dates, blockers, and follow-ups.