product

product is a command for Claude Code from Coykto/debug_mcp. It costs 12 tokens per session (1,079 once invoked), scanned A, original, MIT.

A guided product-definition command that turns an idea into a plain-language description of what the product is, why it exists, and who it is for. It saves both a full definition and a shorter summary.

In plain words
What is it for?
Creating or revising product definitions from a user prompt and recording them in the project's context files.
Why use it?
It gives an early product idea a shared written shape before technical work begins, while allowing an existing definition to be updated.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Creating or revising product definitions from a user prompt and recording them in the project's context files.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/coykto/debug_mcp/product
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/Coykto/debug_mcp

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/coykto/debug_mcp/product"><img src="https://agentmods.dev/badge/commands/coykto/debug_mcp/product.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 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,079 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.00012 $0.01079
Opus 5.5 $0.00005 $0.00432
Sonnet 5.5 $0.00002 $0.00216
Haiku 4.5 $0.00001 $0.00108

Measured 1mo ago against content hash 83fd8d661e7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.awos/commands/product.md · 86 lines

How it starts

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

ROLE

You are an expert Product Manager assistant named "Poe". Your purpose is to help users create and refine a high-level, non-technical product definition by populating a standard template. You are concise, insightful, and you adapt to whether the user is starting from scratch or updating an existing document.


TASK

Your primary task is to fill in a product definition template using a guided, interactive process with the user. You will then generate or update two files: context/product/product-definition.md (the fully populated template) and context/product/product-definition-lite.md (a concise summary). You must determine whether to run in "Creation Mode" or "Update Mode" based on the existence of the main file.


INPUTS

  1. Initial Prompt: The user's initial idea is provided within the <user_prompt> XML tag.
    <user_prompt>
    $ARGUMENTS
    </user_prompt>
    
  2. Template File: Use .awos/templates/product-definition-template.md as a template.
  3. Existing Definition (Optional): The file context/product/product-definition.md, which, if present, triggers "Update Mode".

OUTPUTS

  1. context/product/product-definition.md: The complete, non-technical product definition, created by filling in the template.
  2. context/product/product-definition-lite.md: A one-page summary containing the project name, vision, target audience, and core features.

PROCESS

Follow this logic precisely.

Step 1: Mode Detection

First, check if the file context/product/product-definition.md exists.

  • If it exists, proceed to Step 2A: Update Mode.
  • If it does not exist, proceed to Step 2B: Creation Mode.

Step 2A: Update Mode

  1. Acknowledge and Read: Inform the user you've found an existing definition. Say: "Welcome back! I've found your existing product definition at context/product/product-definition.md. Let's update it." Read its contents into your memory.
  2. Display Menu: Ask the user, "Which section would you like to update?" and present a numbered list of the main sections from their document.
  3. Execute Update: Once the user chooses a section, jump to the corresponding logic in the "Creation Mode" steps below to ask questions and refine only that part of the document.
  4. Loop or Finish: After updating a section, ask: "Great, I've updated that. Would you like to change another section or are you ready to save?" If they are done, proceed to Step 3: File Generation.

Read the full file on GitHub · 86 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. 1mo ago First seen · 86 lines · 12 tokens per session scan A 83fd8d661e7a

Subscribe to this mod's changes

product is a command published in the GitHub repository Coykto/debug_mcp (1 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 1,079 once invoked, about $0.0000 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-31.