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 requirements-analysisgit 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/requirements-analysis)<a href="https://agentmods.dev/skills/omnigentx/jarvis/requirements-analysis"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/requirements-analysis/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/requirements-analysis"><img src="https://agentmods.dev/badge/skills/omnigentx/jarvis/requirements-analysis.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.00032 | $0.00405 |
| Opus 5.5 | $0.00013 | $0.00162 |
| Sonnet 5.5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
requirements-analysis 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.
What it actually says
Requirements Analysis (BA)
⚠️ RESERVED: This skill is prepared for the future BA role. Not currently in use.
Purpose
Guide the Business Analyst role in:
- Gathering and clarifying requirements from stakeholders
- Translating business needs into technical specifications
- Writing acceptance criteria
- Managing scope and priorities
Requirements Process
1. Stakeholder Analysis
- Identify all stakeholders and their interests
- Understand business goals and constraints
- Map relationships between stakeholders
2. Requirements Gathering
- Ask open-ended questions to understand the "why"
- Document user stories: "As a [role], I want [action] so that [benefit]"
- Identify assumptions and constraints
- Prioritize: Must-have vs. Nice-to-have (MoSCoW method)
3. Acceptance Criteria
For each requirement, define:
- Given [precondition]
- When [action]
- Then [expected result]
4. Gap Analysis
- Compare current state vs. desired state
- Identify missing capabilities
- Estimate effort and impact
5. Documentation
- Requirements specification document
- Use case diagrams
- Process flow diagrams
- Traceability matrix
Quality Checks
- Is each requirement testable?
- Is each requirement unambiguous?
- Are requirements complete (no gaps)?
- Are there any contradictions?
- Is the scope clearly bounded?
In Meeting Context
As BA in a meeting:
- Present requirements clearly with acceptance criteria
- Validate that DEV's implementation matches requirements
- Clarify ambiguities when team has questions
- Flag scope creep early
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 · 64 lines · 32 tokens per session scan A 57d295958fa2
requirements-analysis is a skill published in the GitHub repository omnigentx/jarvis (39 stars, last pushed 11d ago), licensed MIT. It adds 32 tokens to every session and 405 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…