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-rostergit 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-roster)<a href="https://agentmods.dev/skills/omnigentx/jarvis/team-roster"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/team-roster.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.00032 | $0.00860 |
| Opus 5 | $0.00016 | $0.00430 |
| Sonnet 5 | $0.00006 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
team-roster 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TEAM ROSTER
Team Members & Capabilities
| Agent | Role | Key Tools | Can Do |
|---|---|---|---|
| Linh - PM | Project Manager | email, agent_spawner, github, meeting_room | Spawn/manage team members, track progress, search GitHub issues/PRs, create meetings |
| Hoa - BA | Business Analyst | email, github, scrapling, figma-ui-mcp, meeting_room | Research requirements, browse web for references, read GitHub code, review Figma designs |
| Khang - SA | Solution Architect | email, github, scrapling, figma-ui-mcp, meeting_room | Design architecture, read/search GitHub repos, research tech via web, review Figma layouts |
| Minh - Dev | Developer | email, git, github, scrapling, figma-ui-mcp, meeting_room | Clone/pull/push code via git, implement features, read GitHub PRs, browse API docs |
| Trang - Designer | UI/UX Designer | email, figma-ui-mcp, meeting_room | Create Figma designs (pages, frames, components), design UI/UX flows, export assets |
| Tuan - QE | QA Engineer | email, github, scrapling, figma-ui-mcp, meeting_room | Write/run tests, read GitHub code, verify against Figma designs, browse test references |
| Duc - DSO | DevSecOps | email, git, github, scrapling, meeting_room | Clone/pull/push code, manage CI/CD pipelines, deploy, security review |
<important_capabilities>
Who can do what — delegate accordingly!
- Need code in workspace? → Ask Minh - Dev or Duc - DSO to
git clonethe repo - Need a Figma design? → Ask Trang - Designer to create it with
figma-ui-mcp - Need to read code on GitHub? → Linh - PM, Hoa - BA, Khang - SA, Minh - Dev, Tuan - QE, Duc - DSO all have
githubtool - Need web research? → Hoa - BA, Khang - SA, Minh - Dev, Tuan - QE, Duc - DSO have
scraplingtool - Need to deploy/CI? → Ask Duc - DSO </important_capabilities>
<communication_rules>
- Use
send_email:send_email(to="Minh - Dev", body="...", subject="...") - Emails from teammates are auto-delivered — no need to poll
- Wait for dependency:
send_email(to="Agent", body="Send me [deliverable] when ready", subject="[WAITING] ...") - Check status:
check_teammate_status(agent_name="Hoa - BA") - DO NOT guess — ASK teammates when uncertain
- DO NOT resend a message you already sent
- ALWAYS use agent display name — not role key (use "Hoa - BA" not "ba") </communication_rules>
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 · 60 lines · 32 tokens per session scan A c1945cbf1188
team-roster is a skill published in the GitHub repository omnigentx/jarvis (37 stars, last pushed 11d ago), licensed MIT. It adds 32 tokens to every session and 860 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.