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 HoangNguyen0403/agent-skills-standard --skill quality-engineering-business-analysisgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/quality-engineering-business-analysis)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-business-analysis"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-business-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/hoangnguyen0403/agent-skills-standard/quality-engineering-business-analysis"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/quality-engineering-business-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.00067 | $0.01299 |
| Opus 5.5 | $0.00027 | $0.00520 |
| Sonnet 5.5 | $0.00013 | $0.00260 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
quality-engineering-business-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 today.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Analysis Standards (Deep Analysis + Story Authoring)
Priority: P0 (CRITICAL)
1. Deep Investigation Protocol
- Behavior-Based AC Decomposition: Define Acceptance Criteria (AC) around one observable behavior per AC; multiple necessary preconditions are permitted. Do NOT split based solely on the word 'And' or condition counts.
- Variable Identification: Extract all Feature Toggles, Market Rules (VN/MY/SG), and User Roles.
- Platform Parity: Verify if logic applies to both Web and Mobile; Flag divergent behavior early.
- Truth Table Verification: Map interacting conditions to a Logic Truth Table; escalate policy decisions to owners rather than selecting business policy silently.
2. Dynamic Actor & Permission Mapping
- Identify all Actors (e.g.,
Customer,Sales Rep,Admin). - Use Actor/Permission Matrix to map specific constraints per Actor.
- Permissions Patterns
3. Edge Case & Boundary Analysis
- State Validation: Verify behavior across all entity (e.g.,
Active,Suspended) and network states. - Boundary Detection: Analyze currency, date, and count limits.
- Negative Testing: Identify flows for Unauthorized Access, Invalid Input, and Null-safety.
4. Anti-Patterns (Analysis)
- No Surface Reading: investigate implications, don't restate.
- No Unowned Unknowns: Carry confirmed evidence and explicit non-critical assumptions. Consequential undefined states block only affected slices (naming owner, consequence, and required input); preserve PARTIAL readiness boundaries. Sensitive changes require technical design and explicit human/governance approval per requirements modeling §1, not blanket P0 blocking.
- Consume shared requirements modeling for preserved stakeholder conflicts, quality review versus need validation, and applicable temporary transition needs; retain existing IDs and only reopen affected slices.
- For general BA/elicitation requests requiring confirmation of captured meaning, directly load the BRD-owned analysis and elicitation procedure without requiring brainstorm-feature or full BRD intake. Participant confirmation does not imply approval.
- No Loose Mapping: Ensure AC aligns 100% with Technical Impact notes.
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.
- today Changed · +2 lines e58efab4b860
- 11d ago Changed · +3 lines cea4b8036c25
- 12d ago Changed 19225c505504
- 1mo ago First seen · 88 lines · 67 tokens per session scan A 3ede6a721b75
quality-engineering-business-analysis is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 1,299 once invoked, about $0.0003 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
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
react-idioms
React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance. Use when developing or refactoring React components and client applications. Pair with typescript-idioms.
elite-engineer
The operating system for elite software engineering in TypeScript, React, and Next.js. Enforces the cognitive models, architecture laws, type-level patterns, component design, visual standards, and performance mandates that separate exceptional software from the ordinary — grounded in named sources (Torvalds…
oma-frontend
Implement or modify web UI in React, Next.js, or Angular. Use for components, pages, styles, forms, and frontend state or data flows.
design-patterns
Frontend design patterns with React 19.2 and TypeScript 6 examples (Composition, Compound Components, Custom Hooks, Render Props, HOC, State Machines). Use when user asks "implement pattern", "use composition", or when designing reusable components.
react-nextjs
React 19.2 + Next.js 16 development - Server Components, Cache Components, proxy.ts, View Transitions, App Router, TypeScript 6, and Tailwind CSS v4. Use when building frontend apps, creating components, or asking "how do I set up X?".