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 manusco/resonance --skill founder-osgit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/founder-os)<a href="https://agentmods.dev/skills/manusco/resonance/founder-os"><img src="https://agentmods.dev/badge/skills/manusco/resonance/founder-os.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 80 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00092 | $0.03164 |
| Opus 5 | $0.00046 | $0.01582 |
| Sonnet 5 | $0.00018 | $0.00633 |
| Haiku 4.5 | $0.00009 | $0.00316 |
Grade A, and why
resonance-ops-founder-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 8d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-founder-os: run the company as a system, not a stream of prompts
Role: the founder's operating system: the rhythm and the guardrails that turn a fleet of specialist skills into a company. Input: a goal to cascade, a week to review, a scorecard to build, a function to delegate, or an authority line to set. Output: an OKR cascade, a company scorecard, a run weekly review,
dec-andmet-entries in the ledger, a cadence spec, or a function's authority budget. Definition of Done: company state lives as typed ledger entries, not prose; every function has one owner and a written authority budget; the recurring work is on a cadence, not on the founder's memory; and work whose proof lands later endsDONE_PENDING_OUTCOMEwith adue:date, not a claim.
A company is not a pile of tasks. It is a small set of numbers that matter, a rhythm that inspects them, and a line between what an agent may do alone and what needs a human. Most of Resonance builds the product. This skill runs the business around it. It holds no company state in prose: decisions are dec- entries, metrics are met- entries, experiments are exp- entries, all in .resonance/ledger/. It reads and writes those. When it delegates, it names the owning skill and the authority that owner has. When it schedules, it writes a spec and hands the timer to the host. It never invents a fact it could cite.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| OKR Cascade | New quarter, or a goal to set | Company to team to this-week, key results as met-/exp- targets |
| Company Scorecard | "What are our numbers" | A KPI tree of met- entries, north-star decomposed into drivers |
| Weekly Business Review / L10 | "Run our weekly review" | What moved, what is stuck, IDS resolutions, and decisions logged as dec- entries |
| Decision Log | A real call was made | A dec- entry, superseded not overwritten, with its evidence edge |
| Delegation | Handing off a function | The owning skill named, the authority budget set |
| Authority Budget | "What can this agent do unasked" | Spend/send/commit/change limits, escalation tiers, a dec- entry |
| Operating Cadence | "What should run when" | A per-function cadence spec plus one host-scheduler example |
What ships with it
10 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.
- evals/01_okr_cascade.json 1.2 KB
- evals/02_weekly_business_review.json 1.4 KB
- evals/03_authority_budget_defense.json 1.3 KB
- evals/04_sandbagging_defense.json 1.2 KB
- references/agent_delegation_map.md 6.4 KB
- references/authority_budgets.md 7.7 KB
- references/kpi_tree.md 6.9 KB
- references/okr_cascade.md 7.1 KB
- references/operating_cadence.md 6.8 KB
- references/weekly_business_review.md 8.1 KB
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.
- 8d ago First seen · 115 lines · 92 tokens per session scan A 9c520a202d46
resonance-ops-founder-os is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 3d ago), licensed MIT. It adds 92 tokens to every session and 3,164 once invoked, about $0.0005 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.