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 fatihkan/badi --skill market-researchgit clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/market-research)<a href="https://agentmods.dev/skills/fatihkan/badi/market-research"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/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/fatihkan/badi/market-research"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/market-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.00000 | $0.00708 |
| Opus 5 | $0.00000 | $0.00354 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
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 4d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research Skills
Structured procedures for validating demand and sizing an opportunity before you build. Pairs with the
market-researcheragent and the/marketcommand; for App Store metrics usebadi market.
Skill List
1. Demand validation
Confirm a real, expressed need exists before committing build time.
- Search the language users actually use (forums, reviews, search suggest, social).
- Distinguish vitamin (nice-to-have) from painkiller (urgent, paid-for) demand.
- Look for existing spend: are people already paying for a worse alternative?
- Output: a demand verdict (strong / weak / none) with the evidence quoted.
2. Niche discovery
Find an under-served, winnable segment instead of a crowded horizontal.
- Decompose a broad market into segments by user, use-case, and platform.
- Score each on demand × competition × your unfair advantage.
- Prefer a narrow segment you can dominate over a wide one you can't.
3. Opportunity sizing
Put a credible number on the prize.
- Top-down (category size × reachable share) sanity-checked bottom-up (reachable users × conversion × price).
- State assumptions explicitly; size a range, not a false-precise point.
- Flag when the honest answer is "too small to matter".
4. Competitor + gap analysis
Map who's already here and where the opening is.
- List incumbents; for each: positioning, pricing, strengths, weak reviews.
- Mine 1-2★ reviews of incumbents for the unmet need to build around.
- Name the specific gap (segment, feature, price point, channel) to win on.
5. Positioning + pricing signal
Decide how to enter, not just whether.
- Anchor pricing to the value/alternative, not cost; find the willingness-to-pay band.
- Draft a one-line positioning: for [who] who [need], [product] is [category] that [benefit].
- Identify the wedge channel where the target user already congregates.
6. Go / shrink / pass decision
Convert research into a decision.
- Synthesize demand + size + gap into a verdict with a confidence level.
- Define the single kill-signal that would reverse a "go".
- Record the read so
/ceo-reviewcan challenge it.
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.
- 4d ago First seen · 59 lines · 0 tokens per session scan A a63274f3a859
market-research is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 708 tokens. 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-09-06.
Other skills, from other repositories
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.