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 agentmods add commands/shyftai/gtmos/switchgit clone --depth 1 https://github.com/shyftai/GTMOSWhat 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 | $0.00012 | $0.00357 |
| Opus 5 | $0.00006 | $0.00179 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
gtm:switch 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 44 lines · 12 tokens per session scan A 4ad3901e1d48
gtm:switch is a command published in the GitHub repository shyftai/GTMOS (42 stars, last pushed 2mo ago), with no licence file. It adds 12 tokens to every session and 357 once invoked, about $0.0001 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 commands, from other repositories
go-to-market
Build a complete go-to-market strategy based on the requirements found in files.requirements.
legal-setup
Set up the legal-compliance skill for your jurisdiction. Walks through jurisdiction selection, source loading, and deadline capture into context/compliance.md. Run once at install; re-run after a fiscal year change or move.
dream
Process my rants. Say "process my rants" or "dream on the rants" (or run /founder-os:dream). Distils unprocessed rants into a 5-line digest and updates patterns, flags, parked decisions, needs-input, client signals, and proposed working preferences as warranted.
legal-update
Refresh legal-compliance source freshness. Walks each source in your jurisdiction's sources.yml, checks for material changes, and updates lastcheckedon dates. Run quarterly or before any client-facing legal memo.
verify
Check that Founder OS is healthy. Say "verify the OS" or "health check" (or run /founder-os:verify). Returns a structured report across 9 substrate checks. Read-only. Never auto-fixes.
os-evolve
Plan the next round of OS improvements. Say "evolve the OS" or run /founder-os:os-evolve [path to an audit or plan]. Scores the last cycle, writes gaps with evidence and numbered execute prompts into one dated plan file. Plans only - never executes its own prompts.