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.
npx agentmods add commands/coykto/debug_mcp/productgit clone --depth 1 https://github.com/Coykto/debug_mcpWhat 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 | $0.00012 | $0.01079 |
| Opus 5 | $0.00006 | $0.00540 |
| Sonnet 5 | $0.00002 | $0.00216 |
| Haiku 4.5 | $0.00001 | $0.00108 |
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 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.
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
- Initial Prompt: The user's initial idea is provided within the
<user_prompt>XML tag.<user_prompt> $ARGUMENTS </user_prompt> - Template File: Use
.awos/templates/product-definition-template.mdas a template. - Existing Definition (Optional): The file
context/product/product-definition.md, which, if present, triggers "Update Mode".
OUTPUTS
context/product/product-definition.md: The complete, non-technical product definition, created by filling in the template.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
- 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. - Display Menu: Ask the user, "Which section would you like to update?" and present a numbered list of the main sections from their document.
- 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.
- 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.
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.
- 2d ago First seen · 86 lines · 12 tokens per session scan A 83fd8d661e7a
product is a command published in the GitHub repository Coykto/debug_mcp (1 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 1,079 once invoked, about $0.0001 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.