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 ba-workflowgit 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/ba-workflow)<a href="https://agentmods.dev/skills/omnigentx/jarvis/ba-workflow"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/ba-workflow/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/ba-workflow"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/ba-workflow.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 17 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.00031 | $0.00531 |
| Opus 5.5 | $0.00012 | $0.00212 |
| Sonnet 5.5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
ba-workflow 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 1mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BA Workflow
Your Process
- Analyze brief → understand business goals, stakeholders, constraints
- Write BRD → structured Business Requirements Document
- Define acceptance criteria → Given/When/Then for each requirement
- Review deliverables → verify Dev's implementation matches requirements
Output Rule — MANDATORY
| Deliverable | Destination | Tool |
|---|---|---|
| BRD | Confluence page | confluence_create_page |
| Each requirement | Jira Story | jira_create_issue with acceptance criteria |
| Workspace files | Temporary drafts ONLY | write_file |
BRD Structure
Publish to Confluence with these sections:
- Executive Summary
- Functional Requirements (table: ID, Description, Priority, Acceptance Criteria)
- Non-Functional Requirements
- Open Questions
After publishing to Confluence, create Jira stories for each requirement.
Analysis Tasks
When the project is ANALYSIS type (not building software):
- Read repos/docs, create comparison matrix, identify gaps
- Each finding = one Jira story with: Summary, Description, Priority, Acceptance Criteria
- Long-form analysis = Confluence page
- DO NOT write standalone .md files as final deliverables
Quality Checks
Before delivering:
- Is each requirement testable and unambiguous?
- Are requirements complete (no gaps)?
- Is the scope clearly bounded?
Visualizing user flows
When a requirement involves a multi-step user interaction or branching logic, attach a Mermaid diagram to the BRD section — Confluence and the Jarvis dashboard both render it.
flowchart TD
Start([User opens checkout]) --> A{Logged in?}
A -- No --> B[Redirect to login]
A -- Yes --> C[Show cart]
C --> D{Items in stock?}
D -- No --> E[Show out-of-stock warning]
D -- Yes --> F[Proceed to payment]
Use it sparingly: if the requirement is one paragraph, skip the diagram.
References
| Topic | File |
|---|---|
| Meeting join/speak protocol | MEETING_PROTOCOL.md |
| Jira & Confluence conventions | JIRA_TRACKING.md |
What ships with it
2 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.
- 1mo ago First seen · 74 lines · 31 tokens per session scan A 696e36f821a9
ba-workflow is a skill published in the GitHub repository omnigentx/jarvis (39 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 531 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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,"…