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.
git clone --depth 1 https://github.com/GktuOktay/ai-skillsWrote 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/rules/gktuoktay/ai-skills/tech-business-analyst)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/tech-business-analyst"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/tech-business-analyst/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/rules/gktuoktay/ai-skills/tech-business-analyst"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/tech-business-analyst.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00489 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
tech-business-analyst 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 8d 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
Technical Business Analyst
This skill bridges Product Design / UX concepts into actionable technical specifications, data models, and developer task breakdowns.
Analysis Methodology
When reviewing a feature or design proposal, conduct a 5-step analysis:
1. Functional Requirements & User Stories
- Break down design into User Stories: As a... I want to... So that...
- Define Acceptance Criteria / Definition of Done using Given-When-Then structure.
2. Data Model & UI State Matrix
- Required Data Fields: Data types (String, Enum, Date) needed by UI components.
- UI State Matrix:
- Loading State: Visual fallback during async fetch.
- Empty State: First-use or empty result behavior.
- Error State: API failures or server error handling.
- Success / Partial State: Behavior on partial data.
3. API & Integration Contracts
- Define endpoints required to support the UI:
GET /api/...(Fetching, pagination, filters)POST / PUT / DELETE(Mutations)
- Provide sample Request/Response JSON payloads.
4. Edge Cases & Boundary Conditions
- Auth / RBAC: Behavior for unauthorized vs admin roles.
- Network/Offline: Handling disconnection or draft preservation.
- Validation Limits: Long text handling, rapid multi-clicks (debounce/throttle requirements).
5. Technical Task Breakdown
Structure tasks for JIRA / GitHub Issues:
- 🔹 Backend Tasks: DB schema changes, API endpoints.
- 🔹 Frontend Tasks: Component building, state wiring, API integration.
- 🔹 Testing Tasks: Verification steps and test coverage.
Output Template
- 🎯 Feature & Spec Summary
- 📋 User Story & Acceptance Criteria
- 🔌 Technical & API Contracts (Sample JSONs + UI State Matrix)
- ⚠️ Critical Edge Cases & Risks
- 🛠️ Developer Task Breakdown (Backend / Frontend / Validation)
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.
- 8d ago First seen · 49 lines · 489 tokens per session scan A 7bca50bb5306
tech-business-analyst is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 489 tokens. 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-09-03.
Other cursor rules, from other repositories
figma-translator
Translate any technical specification into five precise, self-contained Figma Make prompts ready to paste and generate.
canonical__hhadcn-ui
Cursor rule "canonical__hhadcn-ui" from Bilal140202/the-lord-of-the-skills, covering shadcn/ui best practices, installation, initial setup, initialize shadcn/ui in your project and add components as needed.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.