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 jordantplows/claude-skills --skill startup-osgit clone --depth 1 https://github.com/jordantplows/claude-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/jordantplows/claude-skills/startup-os)<a href="https://agentmods.dev/skills/jordantplows/claude-skills/startup-os"><img src="https://agentmods.dev/badge/skills/jordantplows/claude-skills/startup-os/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/jordantplows/claude-skills/startup-os"><img src="https://agentmods.dev/badge/skills/jordantplows/claude-skills/startup-os.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.03928 |
| Opus 5 | $0.00023 | $0.01964 |
| Sonnet 5 | $0.00009 | $0.00786 |
| Haiku 4.5 | $0.00005 | $0.00393 |
Grade A, and why
startup-os 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 — 552 lines — stays where its author put it; the contents beside it link to each section on GitHub.
startup-os · company runtime
This is not a document generator. This is a company operating system.
What it actually is
startup-os is a programming language where .md files ARE the source code.
Each .md file in the department folders and core/ is a self-contained agent with:
- Frontmatter (name, description, role, watches)
- Instructions (what this agent does)
- TypeScript (how it executes)
- Coordination (how it talks to other agents)
The src/ TypeScript runtime loads these .md files and executes them as parallel processes. They coordinate through company.os.json - no direct agent-to-agent calls.
You (the founder) are the only human. Your job is to answer questions agents surface.
Commands
/startup-os build ""
Instantiates a company from an idea.
What happens:
- Parse the idea into initial company profile
- Ask 3 clarifying questions:
- What stage? (idea/validating/building/revenue)
- Who's your first customer? (be specific)
- What must be true for this to work? (key assumption)
- Write answers to
company.os.json - Load all .md agents from disk
- Initialize each agent's department in company.os
- Boot all agents in parallel
- CEO gives first briefing with cross-department status
Example:
/startup-os build "AI-powered code review for security teams"
You'll get a briefing like:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SecureCode · CEO
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WHAT WE'RE BUILDING
AI code review that catches security issues before manual review.
For security engineers at Series B+ SaaS companies.
WHAT YOUR DEPARTMENTS ARE DOING
Product → Defining MVP scope
Legal → Reviewing AI liability for false negatives
Red Team → Challenging "security teams want automation"
FIRST DECISION I NEED
Do you want prototype (2 weeks) or full MVP (8 weeks)?
→ [Type your answer]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
/startup-os ask
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 · 552 lines · 45 tokens per session scan A 6fa55e6db35d
startup-os is a skill published in the GitHub repository jordantplows/claude-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 3,928 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
google-agents-cli-scaffold
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers agents-cli scaffold create, scaffold enhance, and…
google-agents-cli-publish
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the agents-cli publish gemini-enterprise command. Also use when the user wants to "manage agents in Agent Registry"…
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
potpie-change-timeline
Use when an agent needs recent or historical change context: what changed recently, regressions, merged PRs, tickets, docs, incidents, deployments, releases, and source-history ingestion.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.