product-baseline

product-baseline is a skill for Claude Code from spumer/i-m-senior-developer. It costs 108 tokens per session (1,714 once invoked), scanned A, original, MIT.

A limited fallback for product discovery, the process of turning an idea into a clearer problem, outcome, scope, and assumptions. It organizes information already provided by the user and does not perform outside research.

In plain words
What is it for?
Use it to shape ideas, epics, roadmaps, or feature proposals into a consultation draft for a person to review.
Why use it?
It gives a structured draft when no suitable external product-discovery provider is available, while making clear which points are only hypotheses.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the planner plugin — 4 skills, 9 commands, 2 agents shipped together

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.

agentmods
npx agentmods add skills/spumer/i-m-senior-developer/product-baseline
Any agent
npx skills add spumer/i-m-senior-developer --skill product-baseline
Clone the repo
git clone --depth 1 https://github.com/spumer/i-m-senior-developer

Made for: Claude Code.

Or install planner, the plugin that ships this one along with the rest of its 4 skills, 9 commands, 2 agents.

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-baseline

README.md
[![agentmods](https://agentmods.dev/badge/skills/spumer/i-m-senior-developer/product-baseline.svg)](https://agentmods.dev/skills/spumer/i-m-senior-developer/product-baseline)
Your own site
<a href="https://agentmods.dev/skills/spumer/i-m-senior-developer/product-baseline"><img src="https://agentmods.dev/badge/skills/spumer/i-m-senior-developer/product-baseline.svg" alt="Measured on agentmods" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,714 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00108 $0.01714
Opus 5 $0.00054 $0.00857
Sonnet 5 $0.00022 $0.00343
Haiku 4.5 $0.00011 $0.00171

Measured 2d ago against content hash 4061a43437c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

product-baseline 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 2d 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.

plugins/planner/skills/product-baseline/SKILL.md · 112 lines

How it starts

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

Product baseline — встроенный ограниченный поставщик

Назначение и рамка

Минимальная продуктовая проработка, когда подходящего внешнего поставщика нет. Основная команда — скилл product-discovery — вызывает этот скилл последним шагом выбора, после того как внешние кандидаты не прошли: недоступны, покрытие недостаточно или их ответ нарушает договор.

Самостоятельно скилл продуктовую работу не начинает. При доступном внешнем поставщике с полным покрытием встроенный не выбирается.

Честная рамка: у скилла нет доступа к людям, данным о пользователях и внешней проверке. Всё, что он делает, — упорядочивает и формулирует уже принесённое во входе. Новых сведений он не добавляет: порождённые им порядок и гипотезы точек зрения остаются предложениями и гипотезами, а не данными, и помечаются как гипотезы. Он делает вход пригодным для решения человеком. Это запасная ограниченная опора, а не замена внешней продуктовой команды, и ограниченный режим не скрывается: он виден в каждом ответе и попадает в итог запуска основной команды.

Вход

Скилл получает от основной команды:

  1. вид документа (idea, epic, roadmap или feature);
  2. текущую формулировку задачи;
  3. уже собранные утверждения с их типом (наблюдение, внешний источник, допущение, POV-гипотеза, неизвестное);
  4. список требуемых способностей;
  5. явный запрет записи файлов.

Чего во входе нет, того нет у скилла и не появится: недостающее фиксируется в unknowns и limitations, а не додумывается. Утверждение без источника во входе — не наблюдение, а допущение.

Выход

Консультационный черновик с полями:

problem
outcome
actors
scope_in
scope_out
assumptions[]
unknowns[]
candidate_slices[]        # для epic и roadmap
recommended_outcome       # для idea
limitations[]

Правила:

  • обязательны всегда problem, outcome и limitations; ответ без любого из них отклоняется целиком;
  • остальные поля заполняются тем, что есть во входе; пустой перечень честнее выдуманного;
  • каждое утверждение сохраняет свой тип: наблюдение не превращается в проверенный факт, допущение — в знание, гипотеза точки зрения — в отзыв.

Read the full file on GitHub · 112 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. 2d ago Changed · +8 lines 4061a43437c7
  2. 6d ago First seen · 104 lines · 108 tokens per session scan A 7ecda0ba7157

Subscribe to this mod's changes

product-baseline is a skill published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 5d ago), licensed MIT. It adds 108 tokens to every session and 1,714 once invoked, about $0.0005 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-31.

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