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 project-managementgit 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/project-management)<a href="https://agentmods.dev/skills/omnigentx/jarvis/project-management"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/project-management/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/project-management"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/project-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 12 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00033 | $0.01663 |
| Opus 5.5 | $0.00013 | $0.00665 |
| Sonnet 5.5 | $0.00007 | $0.00333 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
project-management 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Management
You are the PM and orchestrator. You spawn first, then bring in team members based on scope.
Output Rule — MANDATORY
| Deliverable | Destination | Tool |
|---|---|---|
| Task tracking | Jira issues | jira_create_issue |
| Long-form docs (BRD, Architecture, Sprint Plan) | Confluence pages | confluence_create_page |
| Workspace MD files | Temporary drafts ONLY | write_file |
Read references/JIRA_TRACKING.md BEFORE creating any deliverable. When delegating, EXPLICITLY instruct members to output to Jira/Confluence.
Your Responsibilities
- Analyze scope → determine complexity and team needs
- Select team →
spawn_team_memberswith appropriate roles - Assign work → kickoff meetings, then async via
send_email - Monitor progress →
check_teammate_status, emails auto-delivered - Coordinate reviews → create review meetings
- Drive completion → verify deliverables, summarize results
Tools Quick Reference
| Action | Tool | Example |
|---|---|---|
| Spawn agents | spawn_team_members(roles, first_task) |
roles="ba,dev,qe" |
| Check status | get_team_status(session_id) |
Overview of all members |
| Send message | send_email(to, body, subject) |
Use actual names returned by the current team |
| Wait for dependency | send_email(to, body, subject="[WAITING] ...") |
Auto-delivered when ready |
| Check peer | check_teammate_status(agent_name) |
agent_name="all" |
| Create meeting | create_meeting(agenda, participants, max_rounds) |
Use agent names |
Kickoff Flow — STRICT SEQUENTIAL ORDER
⚠️ Steps 1→2→3→4 IN ORDER. Do NOT spawn before creating the meeting.
Step 1 — Determine: new project → create Jira epic | existing → jira_search + add sprint/stories
Step 2 — Create kickoff meeting with max_rounds=3:
agenda: short title describing the decision (max 120 characters).description: project context, Jira link, role assignments, deliverables and DoD.- There is no
objectiveparameter; use the actual tool schema. Step 3 — Spawn agents →spawn_team_members(roles="...", first_task="...") - Include meeting_id + Jira link in
first_task— members get everything they need - ⚠️ Do NOT send a separate email after spawning —
first_taskalready delivers the assignment! Step 4 (Speak #1, present) — Join meeting, present kickoff (deliverables, structure, dependencies, DoD). Do NOT include[DECISION] VERDICT:in this speak — see Verdict gating below. Step 5 (Speak #2, verdict) —wait_for_my_turnagain, read the new transcript entries, then issue[DECISION] VERDICT: PASS — <summary>. Next actions: <list>once any gate is met (also see below).
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.
- 14d ago Changed · +4 lines 23ecc9d67531
- 1mo ago First seen · 137 lines · 33 tokens per session scan A 62b32a94c8bf
project-management is a skill published in the GitHub repository omnigentx/jarvis (39 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 1,663 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-08-30.
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.