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 ARCASSystems/FounderOS --skill approval-gatesgit clone --depth 1 https://github.com/ARCASSystems/FounderOSWrote 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/arcassystems/founderos/approval-gates)<a href="https://agentmods.dev/skills/arcassystems/founderos/approval-gates"><img src="https://agentmods.dev/badge/skills/arcassystems/founderos/approval-gates.svg" alt="Measured on agentmods" 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.00083 | $0.00716 |
| Opus 5 | $0.00042 | $0.00358 |
| Sonnet 5 | $0.00017 | $0.00143 |
| Haiku 4.5 | $0.00008 | $0.00072 |
Grade A, and why
approval-gates 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 7d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Approval Gates
Runs on: reasoning - reads your files and reasons; any capable agent can run this.
Pre-Read
Read rules/approval-gates.md. If the installed OS has no customized copy, read templates/rules/approval-gates.md as the fallback.
If neither file exists, default to ask-first for any external, financial, public, destructive, or data-sensitive action.
Action Classes
Classify the requested action into one of these groups:
| Class | Default Gate |
|---|---|
| Internal note, log entry, or draft | Auto-runnable |
| Read-only scan or local analysis | Auto-runnable |
| Edit to operating files with user data | Ask first |
| External send, publish, payment, contract, invoice, or proposal | Ask first |
| Public repo push, public release, or public package update | Ask first |
| Delete, hard reset, force push, secret exposure, or AI attribution in commit history | Refuse unless the user explicitly owns the risk and the action is allowed by repo rules |
The local rules/approval-gates.md wins over this default table.
Procedure
- State the action in one sentence.
- Classify the action type.
- Read the relevant gate from
rules/approval-gates.md. If that file is absent, fall back totemplates/rules/approval-gates.md. If neither exists, use the default table above. - Return one of three calls:
AUTO-RUN- proceed and log if the action changes state.ASK FIRST- show the exact action and wait for yes.REFUSE- explain the blocked action and the safer path.
- If the gate is ambiguous, choose
ASK FIRST.
Approval Artifact
For ask-first actions, present:
Approval needed: <action>
Gate: <rule name or section>
Why approval is needed: <one sentence>
What will change: <files, external party, public surface, money, or data>
Rollback path: <how to undo, or none>
Question: Proceed? yes / no
Logging
If an action changes state after approval, log the outcome to the right file:
brain/log.mdfor operating actions.context/decisions.mdfor resolved decisions.context/clients.mdfor revenue or client state.
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.
- 7d ago First seen · 74 lines · 83 tokens per session scan A 013d45bed582
approval-gates is a skill published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 23d ago), licensed MIT. It adds 83 tokens to every session and 716 once invoked, about $0.0004 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
wiki-ingest
Compile a raw source (document, URL content, meeting notes, research output) into a wikikit agent wiki — merge-don't-overwrite, log contradictions, maintain cross-references, then lint. Use whenever the user says "add this to the wiki", "ingest this", or drops new source material for a wiki maintained with…
publish-report
Publish local HTML, Markdown, or built static web projects with Pagecast as shareable public URLs. Use whenever Codex creates or finishes an .html, .htm, .md, .markdown, or static build output that a person could share (a report, plan, doc, dashboard, or analysis) — proactively offer to publish it without being asked…
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.
alive-search
Search across all walnuts -- decisions, people, files, references, insights, log history.
alive-inbox
Scan 03Inbox/ for unrouted files, present routing suggestions.
founder-voice
Founder voice enforcement for all written output. Apply to any text another person will read.