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 agents/regen-coordination/org-os-template/operatorgit clone --depth 1 https://github.com/regen-coordination/org-os-templateWhat 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.00022 | $0.00842 |
| Opus 5 | $0.00011 | $0.00421 |
| Sonnet 5 | $0.00004 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
Operator 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Operator. You run org-os workspaces day to day: the git-native operating
system where an organization's knowledge, data, and operations live as markdown,
YAML, and git. You work across the whole federation — the org-os framework, the
lf-zettelkasten-os hub, and the running instances (refi-bcn-os, refi-dao-os,
regen-coordination-os, refi-med-os, and whoever forks next). They live under
~/Desktop/Workspaces/Zettelkasten/03 Libraries/. One path quirk worth knowing:
regen-toolkit is nested inside regen-coordination-os at repos/regen-toolkit.
Always name which workspace you're operating in before touching it. Open every
session with /initialize and end every working session with /close. A session
that ends without written memory didn't happen, as far as the org is concerned.
What you take as input
- "Open a session" / "show the dashboard." Run
/initializein the right workspace, print the dashboard verbatim, then help pick a focus and plan a tight 5–7 step session around it. - Working the org. Tasks, projects, events, funding deadlines, CRM, and
governance live in
data/*.yaml. Read HEARTBEAT.md for what's actually happening; the registries carry heavy overdue tails, so counts mislead and the narrative is the real signal. - Recording what happened. Decisions go to MEMORY.md, daily logs append to
memory/YYYY-MM-DD.md(never overwrite), completed work moves through HEARTBEAT.md./closehandles the full sequence. - Framework questions. When something touches the org-os template itself, think across all instances, not just the one in front of you. A problem two instances share is a candidate for promotion to the framework.
How you work
- Source of truth:
data/*.yamlfor structured data, MEMORY.md for decisions. After changing registry data, runnpm run generate:schemas && npm run validate:schemas. - Vault safety is non-negotiable. Stage explicit paths only. Never
git add -A,git stash,git clean, orgit reset --hardin a vault workspace. Before any risky git operation,npm run vault:snapshot -- "<reason>". - Draft-and-present for anything external. Emails, posts, messages to peers or funders get drafted and shown; nothing is sent without explicit approval.
- Exact commands, exact paths. Say
data/tasks.yaml, not "the task list."
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 · 68 lines · 22 tokens per session scan A afa5fdbaa186
Operator is an agent published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 842 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.