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 T4wroot/agentic-seo --skill startupsgit clone --depth 1 https://github.com/T4wroot/agentic-seoWrote 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/t4wroot/agentic-seo/startups)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/startups"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/startups/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/t4wroot/agentic-seo/startups"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/startups.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.00066 | $0.00798 |
| Opus 5.5 | $0.00026 | $0.00319 |
| Sonnet 5.5 | $0.00013 | $0.00160 |
| Haiku 4.5 | $0.00007 | $0.00080 |
Grade A, and why
startups-page-generator 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.
This is a copy
100% identical to startups-page-generator — 80 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pages: Startups / Education
Guides startups and education program pages that offer special pricing or benefits. Targets founders, early-stage teams, students, and educators. Common for SaaS, dev tools, and productivity apps. For channel strategy (discount structure, verification, placement), see education-program.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, pricing, and eligibility.
Identify:
- Program type: Startups, education, nonprofit, incubator
- Offer: Discount, free tier, credits, extended trial
- Eligibility: Criteria (revenue, team size, .edu, etc.)
- Primary goal: Sign up, apply, contact
Page Structure
| Section | Purpose |
|---|---|
| Headline | "Built for Startups" or "Free for Students" |
| Value | Why this program; what they get |
| Eligibility | Who qualifies; how to verify |
| Offer | Discount %, free months, credits |
| Proof | Startups/students who use us |
| CTA | Apply, get started, claim offer |
Best Practices
Eligibility
- Clear criteria: "Pre-seed to Series A" or ".edu email"
- Verification: Application, form, or self-serve
- Abuse prevention: Limit per company; revoke if ineligible
Messaging
- Empathy: "We've been there"; "Grow with us"
- Social proof: "X startups use [Product]"
- Urgency: Limited spots; apply by date (if applicable)
Conversion
- Low friction: Short form; or instant with .edu
- Follow-up: Email sequence for applicants
- Link to pricing: Full pricing for reference
Placement: When Standalone vs Embed
| Approach | When |
|---|---|
| Embed in pricing | Student as tier or block; no separate page; single decision point |
| Registration flow | When discount applies at signup, registration is P0; pricing page P1 |
| Standalone page | /education, /student-discount; when SEO or ad landing needed; avoid if persona "for students" already exists |
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 · 80 lines · 66 tokens per session scan A 7c11c0d50649
startups-page-generator is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 798 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to startups-page-generator, differing in 80 lines, and is treated as a copy.
Other skills, from other repositories
howto-section-generator
When the user wants to create, optimize, or audit a HowTo section block—an in-page block of ordered steps with optional Schema.org HowTo JSON-LD. Also use when the user mentions "HowTo section," "how-to section," "steps section," "quick start," "walkthrough," "tutorial block," "3 steps," "N steps," "simple steps,"…
docs-page-generator
When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions "docs," "documentation site," "docs subdomain," "docs.yourdomain.com," "help center," "knowledge base," "Getting Started," "API Reference," "user guides," or "tutorials." For API marketing landing, use…
seo
Deterministic LLM-first SEO audits for websites, blog posts, and GitHub repositories. Use this when the user asks to "perform SEO analysis", "run SEO audit", "analyze SEO", "check technical SEO", "review schema", "Core Web Vitals", "E-E-A-T", "hreflang", "GEO", "AEO", or GitHub repository SEO optimization. For…
seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking,"…
ai-traffic-tracking
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy…
traffic-analysis
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic…