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/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/omnigentx/jarvis/team-roster"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/team-roster.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00382 |
| Opus 5.5 | $0.00007 | $0.00153 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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 14d 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.
What it actually says
Team roster
Use the current session roster supplied at spawn/resume, or one get_team_status call when ownership is ambiguous. Names are generated per session; never address a static example name or reuse a name from another team. Reserved roles are not active members.
Choose the owner
| Role | Ownership |
|---|---|
| PM | Scope, selective staffing, decision meetings, delivery and acceptance gates |
| BA | Requirements and acceptance criteria |
| SA | Architecture, interfaces and implementation review |
| Dev | Implementation within the authorized workspace |
| Designer | Art/design system, visual and interaction specifications |
| QE | Reproduction, tests and evidence against actual served build |
| DSO | CI, deployment and security review within granted permissions |
A role does not establish tool access. Inspect exposed tools and current agent configuration before declaring a capability absent or requesting another installation. Missing local CLI dependencies do not prove an already-connected MCP is unavailable. Use a harmless scoped capability probe and report its exact outcome.
Coordinate without duplicate work
Send actionable assignments to actual display names in this session. Include checkpoint, output, owner and dependency; do not broadcast when one owner is sufficient. Team messages and status events are delivered automatically; do not poll inbox or repeatedly ask for unchanged status.
Do not reply or acknowledge FYI/no_reply messages. Report new evidence, blockers or deliverables once, linking the artifact instead of forwarding full histories. Escalate a repeated concrete failure to PM with the attempted action and exact error.
Idle means waiting, not completed. Resume a live member through its existing inbox; never start a second process for the same member. PM chooses affected participants for review/retro, and each owner proposes their own reusable lessons using the retrospective skill.
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.
- 14d ago Changed · -29 lines · -14 tokens per session a3f55607f8ec
- 1mo ago First seen · 60 lines · 32 tokens per session scan A c1945cbf1188
team-roster is a skill published in the GitHub repository omnigentx/jarvis (39 stars, last pushed 11d ago), licensed MIT. It adds 18 tokens to every session and 382 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.