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 skills add mlopscommunity/Coding-Agents-Conference-skills --skill product-researchgit clone --depth 1 https://github.com/mlopscommunity/Coding-Agents-Conference-skillsWrote 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.
[](https://agentmods.dev/skills/mlopscommunity/coding-agents-conference-skills/product-research)<a href="https://agentmods.dev/skills/mlopscommunity/coding-agents-conference-skills/product-research"><img src="https://agentmods.dev/badge/skills/mlopscommunity/coding-agents-conference-skills/product-research/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.
<a href="https://agentmods.dev/skills/mlopscommunity/coding-agents-conference-skills/product-research"><img src="https://agentmods.dev/badge/skills/mlopscommunity/coding-agents-conference-skills/product-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00043 | $0.01742 |
| Opus 5 | $0.00022 | $0.00871 |
| Sonnet 5 | $0.00009 | $0.00348 |
| Haiku 4.5 | $0.00004 | $0.00174 |
Grade A, and why
product-research 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 10d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Research with Claude Code
Overview
Two-phase technique for deep product research. First, offload broad information gathering to cheaper deep-research tools (Perplexity, ChatGPT Deep Research). Then feed those raw findings into Claude Code for synthesis, gap analysis, and strategic recommendations.
Core principle: Claude Code with web access is like having 100 researchers on staff. Give it big, open-ended questions. Brain-dump every open question you have stream-of-consciousness. The agent thrives on breadth -- let it surprise you with what it surfaces.
Dependency: Web search access (Claude Code with web tools, or pre-gathered research documents to feed in).
When to Use
- Entering a new market and need competitor landscape mapped
- Preparing for a sales call and need customer org charts, stakeholder priorities, and pain points
- Evaluating build-vs-buy decisions and need feature comparisons across vendors
- Running a quarterly strategy review and need market trends synthesized
- Exploring a new product direction and have dozens of unanswered questions
When NOT to Use
- You need a single factual answer (just search directly)
- The research requires proprietary databases or paywalled sources Claude cannot access
- You need legally verified claims (agent research is a starting point, not a legal opinion)
Common Mistakes
| Mistake | Why it's wrong |
|---|---|
| Asking narrow, specific questions one at a time | You lose the agent's biggest strength: parallel exploration. Dump all your open questions at once and let it find connections you would not have thought of. |
| Running expensive Claude Code tokens on raw information gathering | Deep research tools like Perplexity and ChatGPT are cheaper for the gathering phase. Use Claude Code for the synthesis and strategic thinking, not the initial web crawling. |
| Treating agent output as verified fact | The agent surfaces leads and patterns. Always verify critical claims -- competitor pricing, customer org details, market size figures -- before acting on them. |
| Skipping the brain-dump and writing a polished brief instead | The messier and more complete your question dump, the better. The agent handles ambiguity well. A polished brief often omits the half-formed questions that lead to the best insights. |
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.
- 10d ago First seen · 168 lines · 43 tokens per session scan A 021d48d06ad6
product-research is a skill published in the GitHub repository mlopscommunity/Coding-Agents-Conference-skills (37 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,742 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…