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 Aizaz-Noor/Agent-Startup-Skills --skill market-scoutgit clone --depth 1 https://github.com/Aizaz-Noor/Agent-Startup-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/aizaz-noor/agent-startup-skills/market-scout)<a href="https://agentmods.dev/skills/aizaz-noor/agent-startup-skills/market-scout"><img src="https://agentmods.dev/badge/skills/aizaz-noor/agent-startup-skills/market-scout/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/aizaz-noor/agent-startup-skills/market-scout"><img src="https://agentmods.dev/badge/skills/aizaz-noor/agent-startup-skills/market-scout.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.00046 | $0.00453 |
| Opus 5.5 | $0.00018 | $0.00181 |
| Sonnet 5.5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
market-scout 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- market-scout — 100% identical, 0 lines differ
What it actually says
Market Scout — Research & Validation Agent
Purpose
Prevent building products nobody wants by conducting structured market research before a single line of code is written.
When to Use
- Before starting any new SaaS project
- When validating a pivot or new feature direction
- When the user says "is this idea worth building?"
Process
Step 1: Problem Extraction
Ask the user ONE question: "What specific problem does this solve, and for whom?" Do not proceed until you have a clear answer.
Step 2: Competitor Landscape
Research and present a table of 3-5 existing solutions:
| Competitor | What They Do | Pricing | Key Weakness |
|---|---|---|---|
| Example Co | Solves X for Y | $29/mo | Poor UX for Z |
Step 3: Unique Value Proposition
Based on competitor weaknesses, articulate what makes THIS product different in one sentence. Format: "Unlike [competitor], we [unique advantage] for [target user]."
Step 4: Target User Persona
Define the primary user:
- Role: (e.g., "Solo freelance designer")
- Pain Point: (e.g., "Spends 3 hours/week on invoicing")
- Budget: (e.g., "Willing to pay $10-20/month to save time")
- Current Solution: (e.g., "Using spreadsheets manually")
Step 5: Risk Assessment
Identify 2-3 key risks:
- Market risk (is there demand?)
- Technical risk (can we build this?)
- Monetization risk (will people pay?)
Output
Produce a market_brief.md file with all sections above.
Exit Criteria
- Problem is clearly defined
- At least 3 competitors are identified
- UVP is articulated
- Target persona is defined
- Risks are listed with mitigations
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.
- 1mo ago First seen · 61 lines · 46 tokens per session scan A b8f58a6f63c2
market-scout is a skill published in the GitHub repository Aizaz-Noor/Agent-Startup-Skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 453 once invoked, about $0.0002 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.
Other skills, from other repositories
github
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way. Automatically runs the code-review skill before any commit. Enforces Conventional Commits standard. Handles the full lifecycle: branch → review → commit → push → PR.
prompt-enhancer
TÜRKÇE AÇIKLAMA ─────────────── Bu skill, belirsiz veya eksik bir kullanıcı isteğini alır ve onu daha net, daha spesifik, daha uygulanabilir bir prompt'a dönüştürür. Agent'ın yanlış anlayarak iş yapmasını önler. "Şunu düzelt" gibi muğlak bir istek, "hangi koşulda ne bekleniyor, başarı kriteri ne" formatına çevrilir.
architecture-review
Before committing to an implementation plan, run this skill to stress-test the proposed architecture. Catches over-engineering, circular dependencies, missing failure modes, security gaps, and scalability cliffs — before any code is written. Acts as a "second eye" on the plan.
brainstorming
TÜRKÇE AÇIKLAMA ─────────────── Bu skill, bir fikir veya problemi Sokratik yöntemle rafine eder. Agent sana cevap vermez — sorular sorar. Bu sorular aracılığıyla fikrin netleşir, varsayımlar sorgulanır, kapsam belirlenir ve gerçek ihtiyaç ortaya çıkar. "Ne yapalım?" sorusunu "Tam olarak ne yapmamız gerekiyor ve…
code-review
Systematic code review skill covering both requesting a review (pre-commit checklist) and receiving and responding to review feedback. Checks code quality, security, test coverage, architectural alignment, and documentation before any code is committed.
dependency-audit
Periodically scan project dependencies for security vulnerabilities, outdated packages, and unused dependencies. Produces a prioritized action report. Run before every major release and at least once per month.