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 omnigentx/jarvis --skill team-communicationgit clone --depth 1 https://github.com/omnigentx/jarvisWrote 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/omnigentx/jarvis/team-communication)<a href="https://agentmods.dev/skills/omnigentx/jarvis/team-communication"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/team-communication.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00805 |
| Opus 5 | $0.00021 | $0.00402 |
| Sonnet 5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
team-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 4d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Communication Skill
⚡ Auto status notifications
Team-mate results are auto-delivered to your inbox once ALL members finish:
- A consolidated report (table) with name, status, summary.
- Do NOT poll. Stay focused on your own task; the report arrives when everyone is done.
- If you need richer detail, use
send_emailorcreate_meetingto engage a specific member.
📧 Email — async, fire-and-forget
send_email(to="Name", body="...", subject="...")— send to a specific personsend_email(to="all", body="...")— broadcast to the whole team- Emails from team-mates are auto-delivered into your context — no polling required
Waiting for dependencies
If you need a team-mate's output:
- Send the request:
send_email(to="Agent Name", body="Please send me <deliverable> when ready", subject="[WAITING] ...") - Move on to other work or finish your current task.
- When the team-mate replies, you are auto-woken with the content.
- If you need outputs from several members, call
create_meetingfor a quick sync instead.
🎙️ Meeting — real-time decisions
When you receive 🔔 MEETING INVITE → follow the meeting-participant skill to join and speak.
Email discipline
- Focus on the task first. Only email when you have a deliverable, are blocked, or spot a critical issue. Do NOT email merely to update status or acknowledge.
- Concise but complete. Include enough context. Use subject prefixes:
[DONE],[BLOCKED],[BUG],[REVIEW],[DELIVERABLE],[WAITING]. - Use CC sparingly. Only CC people who genuinely need to know.
- Do NOT reply just to acknowledge. Use
no_reply=Truefor FYI messages. - Avoid email ping-pong. If you need back-and-forth, schedule a meeting instead of emailing.
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.
- 4d ago First seen · 66 lines · 42 tokens per session scan A 11fccd46987e
team-communication is a skill published in the GitHub repository omnigentx/jarvis (36 stars, last pushed 11d ago), licensed MIT. It adds 42 tokens to every session and 805 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.