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 mshadmanrahman/pm-pilot --skill market-researchgit clone --depth 1 https://github.com/mshadmanrahman/pm-pilotWrote 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/mshadmanrahman/pm-pilot/market-research)<a href="https://agentmods.dev/skills/mshadmanrahman/pm-pilot/market-research"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/market-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/mshadmanrahman/pm-pilot/market-research"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/market-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 66 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00042 | $0.00519 |
| Opus 5 | $0.00021 | $0.00260 |
| Sonnet 5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
market-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 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.
What it actually says
Market Research
Competitive analysis with source attribution.
Trigger
"market research", "competitive analysis", "competitor comparison"
Tools
WebSearch, Exa, WebFetch, any available research MCP tools.
Process
- Scope: Confirm market, competitors, and dimensions to evaluate (pricing, features, positioning, audience).
- Research: Fan out parallel searches:
- Company websites (pricing pages, feature lists, about pages)
- Review sites (G2, Capterra, TrustRadius)
- News and press releases (recent funding, launches, pivots)
- Social proof (case studies, testimonials, community size)
- Synthesize: Compile into structured output.
Output Format
# Market Research: {topic}
## Market Overview
- Market size and growth trajectory
- Key trends shaping the space
- Buyer segments and their priorities
## Competitor Comparison Matrix
| Dimension | Competitor A | Competitor B | Competitor C | Our Position |
|-----------|-------------|-------------|-------------|-------------|
| Pricing | ... | ... | ... | ... |
| Key Features | ... | ... | ... | ... |
| Target Audience | ... | ... | ... | ... |
| Strengths | ... | ... | ... | ... |
| Weaknesses | ... | ... | ... | ... |
## Key Findings
1. {Insight with implication}
2. {Insight with implication}
3. {Insight with implication}
## Opportunities
- {Gap we can exploit}
- {Underserved segment}
## Sources
- [Source title](url) - accessed {date}
- [Source title](url) - accessed {date}
Rules
- Every claim must have a cited source. Tag with
[Source: {url or name}]. - Distinguish facts from inference. Tag speculation with
[Assumption]. - Tag metrics without verification with
[Needs data]. - Prefer primary sources (company sites, SEC filings) over secondary (blog posts, tweets).
- Date all findings; markets shift fast.
- If data is unavailable, say so. Never fabricate.
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.
- 12d ago First seen · 70 lines · 42 tokens per session scan A b0128176908b
market-research is a skill published in the GitHub repository mshadmanrahman/pm-pilot (20 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 519 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
build-implementation
Generate context-aware implementation prompts for a selected growth loop. Use when the user says "build", "implement", "generate code", "create prompt", or "how do I build this".
analyze-codebase
Run comprehensive PLG analysis on a codebase to detect tech stack, existing growth features, and revenue opportunities. Use when the user says "analyze", "scan", "audit codebase", or "find growth opportunities".
deploy-telemetry
Set up analytics and tracking infrastructure for growth loops. Use when the user says "deploy telemetry", "set up analytics", "tracking", "events", "push to supabase", or "skene push".
plan-growth-loop
Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth loops", "prioritize", "what should I build", or "roadmap".
validate-loop
Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".
initialize-config
Set up Skene configuration for a project. Use when starting a new PLG analysis, when .skene.config is missing, or when the user says "skene init", "set up skene", or "configure skene".