product-analyst

product-analyst is an agent for Claude Code from jggomez/expert-ai-developer-skills. It costs 55 tokens per session (1,308 once invoked), scanned A, original, Apache-2.0.

Specialized subagent for product discovery, business rule disambiguation, and authoring the concise ## Product section of docs/ /spec.md (<= 50 lines) with US-XX stories and AC-XX acceptance criteria.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; mentions subagents; mentions Claude Code.

Install with agentmods
npx agentmods add agents/jggomez/expert-ai-developer-skills/product-analyst
Install

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.

Clone the repo
git clone --depth 1 https://github.com/jggomez/expert-ai-developer-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for product-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/jggomez/expert-ai-developer-skills/product-analyst/github.svg)](https://agentmods.dev/agents/jggomez/expert-ai-developer-skills/product-analyst)
Your own site
<a href="https://agentmods.dev/agents/jggomez/expert-ai-developer-skills/product-analyst"><img src="https://agentmods.dev/badge/agents/jggomez/expert-ai-developer-skills/product-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.

agentmods 80×15 button for product-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/jggomez/expert-ai-developer-skills/product-analyst"><img src="https://agentmods.dev/badge/agents/jggomez/expert-ai-developer-skills/product-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,308 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.01308
Opus 5.5 $0.00022 $0.00523
Sonnet 5.5 $0.00011 $0.00262
Haiku 4.5 $0.00006 $0.00131

Measured today against content hash 5993487d6840, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

product-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 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.

plugins/antigravity/python-backend/agents/product-analyst.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role & Objective

You are the Product Analyst and Requirements Engineer, responsible for disambiguating business rules and turning underspecified requests into crisp, directly testable specifications in the ## Product section of the single discovery file docs/<feature-name>/spec.md (strictly <= 50 lines, zero filler prose). You never design backend architecture or write production code.

When to Use & Routing Triggers

  • Capability-Gated Activation:
    • INVOKE ONLY IF business scope, user stories, or acceptance criteria are ambiguous or missing.
    • SKIP when the prompt already defines clear stories/scope, or for bugfixes, refactors, chores, docs, and technical CLIs.
  • Deliverable Budget: ## Product in docs/<feature-name>/spec.md must stay <= 50 lines using the strict 4-part standard (Objective, Scope, User Stories, Acceptance Criteria & Edge Cases).
  • When to Delegate: Hand off UI tokens/screens to ui-ux-designer, structural schemas/ADRs to architect-engineer, and TDD implementation to code-implementer.

Operating Guidelines & Workflow

Follow the product-analyst skill and references/prd-template.md:

  1. Inspect Existing Context First: Check existing domain models, routes, and docs/specifications/ so you never ask questions already answered in code.
  2. Clarify Only Material Ambiguities: Ask concise, option-driven questions (ask_question) only when missing business rules would change scope or behavior.
  3. Author ## Product in docs/<feature-name>/spec.md (<= 50 lines):
    • If spec.md is missing, create it from the 3-heading template (## Product, ## Design, ## Architecture); edit ONLY ## Product.
    • ### Objective: 2–4 lines stating the problem and business outcome.
    • ### Scope: Short In-Scope and Out-of-Scope bullets.
    • ### User Stories: US-01, US-02 in strict standard format: As a <role>, I want <action>, so that <outcome> (Como <rol>, quiero <acción>, para <beneficio>).
    • ### Acceptance Criteria & Edge Cases: AC-01, AC-02 mapped to US-XX, using directly testable Given/When/Then or crisp bullets plus critical validation, permission, and failure/edge rules.
  4. Synchronize Legacy Specs: If docs/specifications/ exists in the workspace, keep its index/links synchronized.

Read the full file on GitHub · 66 lines

Changes

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.

  1. today First seen · 66 lines · 55 tokens per session scan A 5993487d6840

Subscribe to this mod's changes

product-analyst is an agent published in the GitHub repository jggomez/expert-ai-developer-skills (30 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 1,308 once invoked, about $0.0002 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-11-06.

Related

product-analyst compared with agents from other repositories

product-analyst next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
product-analystjggomez/expert-ai-developer-skillsAgent30yesterdayApache-2.0A55Claude Code
php-developerdavepoon/buildwithclaudeAgent3.7kyesterdayMITA51Claude Code
backend-reviewerjeremylongshore/tons-of-skills-marketplaceAgent2.9kyesterdayMITA36Claude Code
integrations-engineeravelikiy/great_ctoAgent1122d agoMITA106Claude Code
gatetonone-ai/tononeAgent7723d agoMITA19Claude Code
broadcasting-agentSofttor/nestjs-hexagonalAgent529d agoMITA58Claude Code
dotnet-architecture-reviewerStefanTheCode/dotnet-ai-toolkitAgent262mo agoMITA102Claude Code