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 forjd/startup-ideation-skills --skill startup-v1-feasibilitygit clone --depth 1 https://github.com/forjd/startup-ideation-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/forjd/startup-ideation-skills/startup-v1-feasibility)<a href="https://agentmods.dev/skills/forjd/startup-ideation-skills/startup-v1-feasibility"><img src="https://agentmods.dev/badge/skills/forjd/startup-ideation-skills/startup-v1-feasibility/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/forjd/startup-ideation-skills/startup-v1-feasibility"><img src="https://agentmods.dev/badge/skills/forjd/startup-ideation-skills/startup-v1-feasibility.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.00040 | $0.01877 |
| Opus 5 | $0.00020 | $0.00938 |
| Sonnet 5 | $0.00008 | $0.00375 |
| Haiku 4.5 | $0.00004 | $0.00188 |
Grade A, and why
startup-v1-feasibility 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 11d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Startup V1 Feasibility
When to use
Use when a captured, grilled, and validated startup problem has enough evidence to justify deciding what to build first.
This skill prevents v1 scope creep. The first version should test the riskiest useful assumption, not become a miniature version of the imagined company.
If the user has not run a validation test or cannot provide credible evidence from real prospects, do not produce a build plan by default. Return a Not build-ready verdict, list the missing evidence, and route them back to validation. Only produce a planning-only sketch when the user explicitly asks for a hypothetical plan and label it as unvalidated.
Core principle
A good v1 is small enough to build in 2–4 weeks and sharp enough that real user behaviour teaches something commercially useful.
Workflow
- Start from the evidence packet, problem ledger, grilling notes, and validation results.
- Check the v1 evidence gate before scoping:
- Specific target user and buyer are known.
- Current workaround and cost are grounded in real examples.
- Founder advantage, recent enabling change, and first distribution route are plausible.
- There is at least a rough expansion path beyond the first wedge.
- At least one validation test produced behavioural signal, not compliments.
- The strongest remaining assumption is one a v1 can test.
- If the gate fails, stop and return the missing evidence plus the next validation move.
- Identify the narrow wedge: the painful sliver where a first product can deliver value.
- Identify the riskiest assumption that building can test.
- Choose a v1 mode: manual concierge, Wizard-of-Oz, internal tool, workflow wrapper, integration, report, landing page plus manual fulfilment, narrow automation, or paid pilot.
- Define the smallest user journey that proves value.
- Cut scope until it is almost uncomfortable.
- List what is explicitly out of scope.
- Define success and kill criteria before implementation.
- Produce a 2–4 week build plan only if the evidence gate and scope are credible.
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.
- 11d ago First seen · 263 lines · 40 tokens per session scan A 0ca2b2626834
startup-v1-feasibility is a skill published in the GitHub repository forjd/startup-ideation-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,877 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-31.
Other skills, from other repositories
hunt-auth-bypass
Hunting skill for auth bypass vulnerabilities. Built from 12 public bug bounty reports across SAML XSW / parser-differential (GitHub Enterprise CVE-2025-25291/25292), SAML signature stripping (Uber, Rocket.Chat, samlify CVE-2025-47949), SAML domain enforcement bypass via control characters (HackerOne 2024)…
m365-entra-attack
Microsoft 365 / Entra ID red-team attack chain — current 2026 reality. AADSTS code reference, user enumeration vectors (with hardening status), Smart Lockout math, Conditional Access bypass options, ROPC + SAML SSO browser flow, Burp/Playwright templates. Built from authorized red-team work where ROPC spray surfaced…
password-spray-methodology
End-to-end password spray playbook. User enumeration, lockout detection, password pattern generation, spray execution across all protocols, error code differentials, and engagement discipline. Unifies M365/Entra, Okta, Exchange, Kerberos, SharePoint, XMLRPC, OIDC, and AD SMB/WinRM spraying into one methodology.
subdomain-enumeration
Map subdomains via crt.sh and subfinder at recon kickoff.
cache-attack
Poison CDN cache or deceive when X-Cache header is detected.
hunt-django
Hunt Django-specific vulnerabilities: DRF permission gaps, ORM injection, and admin exploitation.