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 agentmods add skills/omnigentx/jarvis/ba-workflownpx 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.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00031 | $0.00531 |
| Opus 5 | $0.00015 | $0.00266 |
| Sonnet 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 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 — 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.
- 4d ago First seen · 74 lines · 31 tokens per session scan A 696e36f821a9
ba-workflow is a skill published in the GitHub repository omnigentx/jarvis (36 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 531 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…