agentmods.dev

reviewing-product-strategy

reviewing-product-strategy is a skill for Claude Code, Codex from porcupine-md/jonggrang. It costs 30 tokens per session (438 once invoked), scanned A, original, MIT.

A founder-style review process for questioning a product plan and looking for a more valuable version of the product. It examines the target customer, the problem, the assumptions, and the proposed scope.

In plain words
What is it for?
Use it to review a feature pitch or plan, test demand, identify the exact users who need it, challenge the approach, and recommend expanding, refining, or holding the scope.
Why use it?
It helps reveal whether a feature solves an urgent problem and whether the plan is too narrow, too broad, or appropriately sized.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 11repo 4d ago A scan 30 tokens original MIT

Good fit Use it to review a feature pitch or plan, test demand, identify the exact users who need it, challenge the approach, and recommend expanding, refining, or holding the scope.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/porcupine-md/jonggrang/reviewing-product-strategy
View source ↗ porcupine-md/jonggrang jonggrang.dev
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.

Any agent
npx skills add porcupine-md/jonggrang --skill reviewing-product-strategy
Clone the repo
git clone --depth 1 https://github.com/porcupine-md/jonggrang

Made for: Claude Code, Codex.

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 reviewing-product-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/porcupine-md/jonggrang/reviewing-product-strategy/github.svg)](https://agentmods.dev/skills/porcupine-md/jonggrang/reviewing-product-strategy)
Your own site
<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/reviewing-product-strategy"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/reviewing-product-strategy/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 reviewing-product-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/reviewing-product-strategy"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/reviewing-product-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 438 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.00030 $0.00438
Opus 5 $0.00015 $0.00219
Sonnet 5 $0.00006 $0.00088
Haiku 4.5 $0.00003 $0.00044

Measured 12d ago against content hash 6aa8fd3f8d15, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

reviewing-product-strategy 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 12d 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.

skills/core/reviewing-product-strategy/SKILL.md · 34 lines

What it actually says

Reviewing Product Strategy (CEO Review)

Role Constraints: Lead (Write/Bash access allowed). File Access: Do NOT use literal placeholders for file paths. Use the glob tool to search for the active feature directory under .jonggrang/.output/features/.

Objective

Rethink the problem, find the 10-star product, challenge premises, and expand scope when it creates a better product. Think like a CEO/Founder.

Execution Steps

  1. Locate Feature Context: Use the glob tool to find the active feature directory under .jonggrang/.output/features/ and read the pitch.md or plan.md.
  2. Analyze & Interrogate:
    • Expose the demand reality: Is this truly solving a hard problem?
    • Challenge the status quo: Why hasn't this been solved this way before?
    • Desperate specificity: Who exactly is desperate for this?
  3. Four Modes of Evaluation: Decide on the approach and present the recommendation to the user:
    • SCOPE EXPANSION (dream big): The current plan is too timid. What is the 10-star version?
    • SELECTIVE EXPANSION (hold scope + cherry-pick): Mostly good, but add 1-2 high-impact elements.
    • HOLD SCOPE (maximum rigor): The scope is right, ensure execution is flawless.
    • SCOPE REDUCTION (strip to essentials): The plan is bloated. Cut it down to the MVP.
  4. Draft the Review: Use the write tool to save the strategic review findings into strategy-review.md in the active feature directory. Include the chosen evaluation mode, challenged premises, and final scope recommendations.

Completion Signal

When the strategy review is complete and the file is written, output exactly:

STRATEGY_REVIEW_COMPLETE

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. 12d ago First seen · 34 lines · 30 tokens per session scan A 6aa8fd3f8d15

Subscribe to this mod's changes

reviewing-product-strategy is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 438 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.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens