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 Maudeunfledged834/startup-founder-skills --skill startup-contextgit clone --depth 1 https://github.com/Maudeunfledged834/startup-founder-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/maudeunfledged834/startup-founder-skills/startup-context)<a href="https://agentmods.dev/skills/maudeunfledged834/startup-founder-skills/startup-context"><img src="https://agentmods.dev/badge/skills/maudeunfledged834/startup-founder-skills/startup-context/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/maudeunfledged834/startup-founder-skills/startup-context"><img src="https://agentmods.dev/badge/skills/maudeunfledged834/startup-founder-skills/startup-context.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.00045 | $0.00874 |
| Opus 5.5 | $0.00018 | $0.00350 |
| Sonnet 5.5 | $0.00009 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
startup-context 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 startup-context — 0 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Startup Context
This is the foundation skill. Every other skill reads this context first to produce tailored, specific output instead of generic advice.
When to Use
- First time a user runs any skill and no context file exists
- When the user says "let me tell you about my startup" or similar
- When any skill detects missing context and needs to gather it
Workflow
- Check for existing context — look for
.agents/startup-context.mdin the project root - If missing, interview the founder — ask the questions below, one section at a time
- Generate the context file — write structured markdown to
.agents/startup-context.md - Keep it updated — when the user shares new info that changes context, update the file
Context Document Structure
# Startup Context
## Company
- **Name:**
- **One-liner:** (what you do in one sentence)
- **Stage:** (idea / pre-seed / seed / series A / series B / growth)
- **Founded:** (date)
- **Location:** (city/remote)
- **Legal entity:** (Delaware C-Corp, LLC, etc.)
## Product
- **What it does:** (2-3 sentences)
- **Category:** (e.g., developer tools, fintech, healthtech)
- **Platform:** (web app, mobile, API, desktop, hardware)
- **Tech stack:** (languages, frameworks, infra)
- **Current state:** (idea, prototype, beta, launched, scaling)
## Market
- **Target customer:** (who buys / who uses — be specific)
- **ICP:** (ideal customer profile — industry, size, role, pain)
- **TAM/SAM/SOM:** (if known)
- **Competitors:** (top 3-5, how you differ)
- **Positioning:** (why you vs alternatives)
## Business Model
- **Revenue model:** (SaaS, usage-based, marketplace, etc.)
- **Pricing:** (current pricing or planned)
- **Current MRR/ARR:** (if applicable)
- **Key metrics:** (the 3-5 numbers you track most)
## Team
- **Founders:** (names, roles, backgrounds)
- **Team size:**
- **Key hires needed:**
- **Advisors/board:**
## Fundraising
- **Total raised:**
- **Last round:** (amount, date, lead investor)
- **Current runway:** (months)
- **Next raise:** (target amount, timeline, what it's for)
## Goals
- **Next 3 months:**
- **Next 12 months:**
- **Biggest challenge right now:**
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 · 104 lines · 45 tokens per session scan A ea942c8c49f1
startup-context is a skill published in the GitHub repository Maudeunfledged834/startup-founder-skills (8 stars, last pushed 16d ago), licensed MIT. It adds 45 tokens to every session and 874 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to startup-context, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
assigns-audit
Inspect LiveView socket assigns for memory bloat — missing temporaryassigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporaryassigns.
recall
Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.
compound
Document solved problems to compound team knowledge. Creates categorized docs with YAML frontmatter. Triggers on "that worked", "it's fixed", "compound".