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 saitarrun/Devforge-ai --skill startup-lifecyclegit clone --depth 1 https://github.com/saitarrun/Devforge-aiWrote 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/saitarrun/devforge-ai/startup-lifecycle)<a href="https://agentmods.dev/skills/saitarrun/devforge-ai/startup-lifecycle"><img src="https://agentmods.dev/badge/skills/saitarrun/devforge-ai/startup-lifecycle.svg" alt="Measured on agentmods" 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.00045 | $0.00763 |
| Opus 5 | $0.00023 | $0.00381 |
| Sonnet 5 | $0.00009 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
startup-lifecycle 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 3d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Startup Full Lifecycle & Growth Skill
This skill guides founders and engineering teams through building, launching, operating, monetizing, and scaling a high-growth SaaS / AI startup directly from the repository.
1. The Startup Growth Engine Matrix
[Phase 1: 0 to 1 — Problem-Market Fit & MVP]
↳ Grill-Me Ideation → Scope Minimization (3 Tracer Slices) → Landing Page Waitlist + Stripe Pre-orders
↓
[Phase 2: 1 to 10 — Product-Market Fit (PMF) & Telemetry]
↳ PostHog / Mixpanel Event Tracking → North Star Metric → Sean Ellis PMF Survey (>40% "Very Disappointed")
↓
[Phase 3: 10 to 100 — SaaS Monetization & Growth Loops]
↳ Stripe Billing / Polar / LemonSqueezy (Subscriptions, Metered Tokens, Team Seats) → Referral & SEO Loops
↓
[Phase 4: Scale — Unit Economics & Operational Governance]
↳ Churn & Retention Cohorts → LTV / CAC Ratio (>3:1) → SOC2 / Compliance → Self-Serve Enterprise Upgrades
2. Startup Engineering Standards
A. SaaS Monetization & Pricing Architecture
- Pricing Models:
- Tiered Subscriptions: Free / Starter / Pro / Enterprise.
- Usage-Based (Metered): Bill per API call, token consumed, or storage GB.
- Per-Seat: Scaled pricing per team member.
- Billing Provider Integration: Stripe Elements, Customer Portal, Webhook Handlers (
invoice.payment_succeeded,customer.subscription.deleted), and dunning email triggers.
B. Founder Telemetry & Analytics Instrumentation
- North Star Metric: Track the one event indicating primary user value (e.g.
query_executed,report_exported,claim_processed). - Funnel Drop-Off Tracking:
User Visited Landing Page→Signed Up→Completed Onboarding→Invited Teammate→Paid.
- Feature Flags & A/B Testing: PostHog / LaunchDarkly flags to test pricing experiments and checkout flows safely.
C. Automated Customer Feedback & Churn Mitigation
- NPS & In-App Surveys: Automated survey trigger after 7 days of active usage.
- Cancellation Flow: Capture exit reason (Too expensive, missing feature, buggy, switched to competitor) and trigger discount/rescue offer.
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.
- 3d ago First seen · 63 lines · 45 tokens per session scan A f96911906947
startup-lifecycle is a skill published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 45 tokens to every session and 763 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-09-03.
Other skills, from other repositories
batch
Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.
prep
Spec a ticket before it is dispatched. Brainstorms it, decides everything it can recommend an answer for, asks a present human about the little that survives, and leaves the spec, the decisions and anything still open as one ticket comment. No worktree, no branch, no pull request, and the ticket stays where it was.
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it. Use when asked to work a ticket end-to-end.
g-init
The single G-Forge front door — run once after installing the plugin. Detects what's here and routes to /g-onboard (existing codebase) or /g-kickoff (new project) for the brief, scaffolds CLAUDE.md (compact G-rules), g-docs/ROADMAP.md (with the Active Session handoff), g-docs/milestones/, g-docs/todo.md, the…
g-onboard
Onboard G-Forge onto an existing codebase. Reads deeply before asking anything — treats existing CLAUDE.md, rules, agents, and task ledgers as first-class inputs. Only interviews for what it genuinely doesn't know yet. Produces or updates g-docs/projectbrief.md.
g-roadmap
Project-manager-driven milestone planner. Gated phases — feature dump → cluster → sequence → premortem & re-prioritize → approve → write. Narrates reasoning at every step, and runs a premortem + re-prioritization of the whole roadmap whenever a milestone is added or modified. Auto-triggers when no g-docs/ROADMAP.md…