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 mrDesign-ww/vault-os --skill team-communicationsgit clone --depth 1 https://github.com/mrDesign-ww/vault-osWrote 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/mrdesign-ww/vault-os/team-communications)<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/team-communications"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/team-communications/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/team-communications"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/team-communications.svg" alt="Reviewed on agentmods" width="80" 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.00148 | $0.00954 |
| Opus 5 | $0.00074 | $0.00477 |
| Sonnet 5 | $0.00030 | $0.00191 |
| Haiku 4.5 | $0.00015 | $0.00095 |
Grade A, and why
team-communications 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 9d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal Comms
Originally contributed by maximcoding — enhanced and integrated by the claude-skills team.
Write polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.
Routing
Identify the communication type from the user's request, then read the matching reference file before writing anything:
| Type | Trigger phrases | Reference file |
|---|---|---|
| 3P Update | "3P", "progress plans problems", "weekly team update", "what did we ship" | references/3p-updates.md |
| Newsletter | "newsletter", "company update", "weekly/monthly roundup", "all-hands summary" | references/company-newsletter.md |
| FAQ | "FAQ", "common questions", "what people are asking", "confusion around" | references/faq-answers.md |
| General | anything internal that doesn't match above | references/general-comms.md |
If the type is ambiguous, ask one clarifying question — don't guess.
Workflow
- Read the reference file for the matched type. Follow its formatting exactly.
- Gather inputs. Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.
- Clarify scope. Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
- Draft. Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
- Present the draft and ask if anything needs to be added, removed, or reworded.
Tone & Style (applies to all types)
- Use "we" — you are part of the company.
- Active voice, present tense for progress, future tense for plans.
- Concise. Every sentence should carry information. Cut filler.
- Include metrics and links wherever possible.
- Professional but approachable — not corporate-speak.
- Put the most important information first.
What ships with it
4 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.
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.
- 9d ago First seen · 68 lines · 148 tokens per session scan A b6b7e1ce17fb
team-communications is a skill published in the GitHub repository mrDesign-ww/vault-os (2 stars, last pushed yesterday), licensed MIT. It adds 148 tokens to every session and 954 once invoked, about $0.0007 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
ln-62-repository-publisher
Commits, pushes, and remotely verifies authorized repository changes. Not for releases, package publication, or announcements.
remove
Remove a deployed framework or addon from the current workspace.