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 omer-metin/skills-for-antigravity --skill founder-operating-systemgit clone --depth 1 https://github.com/omer-metin/skills-for-antigravityWrote 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/omer-metin/skills-for-antigravity/founder-operating-system)<a href="https://agentmods.dev/skills/omer-metin/skills-for-antigravity/founder-operating-system"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/founder-operating-system/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/omer-metin/skills-for-antigravity/founder-operating-system"><img src="https://agentmods.dev/badge/skills/omer-metin/skills-for-antigravity/founder-operating-system.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.00076 | $0.00764 |
| Opus 5.5 | $0.00030 | $0.00306 |
| Sonnet 5.5 | $0.00015 | $0.00153 |
| Haiku 4.5 | $0.00008 | $0.00076 |
Grade A, and why
founder-operating-system 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.
How it starts
The opening of the file, as written. The whole thing — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Founder Operating System
Identity
Principles
- {'name': 'Maker schedule vs manager schedule', 'description': 'Makers need long uninterrupted blocks. Managers work in hour chunks.\nFounders are both. Protect maker time ruthlessly. Batch manager work.\nA single meeting can blow a whole afternoon of maker work.\n', 'source': "Maker's Schedule, Manager's Schedule", 'examples': {'good': 'Mornings are maker time, no meetings. Afternoons for calls.', 'bad': 'Meetings scattered throughout day, never deep work.'}}
- {'name': 'Default alive or default dead', 'description': 'If you maintain current growth and burn, will you become profitable before\nrunning out of money? Know which you are. Default dead requires immediate\naction - cut burn, accelerate growth, or raise money.\n', 'source': 'Default Alive or Default Dead', 'examples': {'good': 'We are default dead. Here is our plan to become default alive.', 'bad': 'We have 8 months runway, we will figure it out.'}}
- {'name': 'How to lose time and money', 'description': 'Time and money slip away in small increments, not big ones. A little\nfeature creep. A slightly higher burn. The path to failure is gradual,\nnot sudden. Watch the small things.\n', 'source': 'How to Lose Time and Money', 'examples': {'good': 'Weekly review of where time and money went', 'bad': 'Assuming big decisions matter, ignoring daily choices'}}
- {'name': 'Writing is thinking', 'description': 'Unclear writing is unclear thinking. If you cannot write it clearly, you\ndo not understand it. Writing forces clarity. Founders should write\nregularly - investor updates, memos, public posts.\n', 'source': 'Write Like You Talk', 'examples': {'good': 'Weekly written reflection on what was learned', 'bad': 'Never writing, assuming verbal communication sufficient'}}
- {'name': 'Strong opinions, loosely held', 'description': 'Have conviction to move forward, but update when evidence changes. The\nability to disagree and commit, then revise, is essential. Neither\nstubborn nor wishy-washy.\n', 'source': 'How to Disagree', 'examples': {'good': 'Clear position, but update the moment new evidence arrives', 'bad': 'Either refusing to commit or changing position constantly'}}
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 29 lines · 76 tokens per session scan A 418348fc5362
founder-operating-system is a skill published in the GitHub repository omer-metin/skills-for-antigravity (183 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 764 once invoked, about $0.0003 per session on Opus 5.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
interview-me
An interview skill that asks one question at a time to uncover what a user actually needs. It is intended for unclear requests, before a plan, specification, or code exists.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
kyc-escalation
Write an internal KYC/AML escalation memo: a factual time-stamped trigger description, customer-profile vs activity mismatch analysis, red-flag taxonomy mapping, outstanding information, and a recommendation with rationale. Use when asked to escalate a KYC alert, document an AML concern, write up unusual-activity…
agent-era-pricing
Redesign seat-based pricing for the agent era — when one human runs ten agents, per-seat models collapse. Use when agents are eroding seat counts, when asked to migrate to usage- or outcome-based pricing, to price an agent/API tier, or to defend revenue as customers automate their own usage. Produces a pricing…
ai-roi-audit
Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with…
credit-memo
Write a credit memo for a lending decision: borrower story, facility structure, repayment sources, financial-ratio spread with covenant headroom, risk factors with mitigants, risk-rating rationale, and a recommendation. Use when asked to write a credit memo, credit application, credit paper, loan write-up, or prepare…