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 skills/regen-coordination/org-os-template/initializenpx skills add regen-coordination/org-os-template --skill initializegit 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.00031 | $0.00395 |
| Opus 5 | $0.00015 | $0.00198 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
initialize 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 3d 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.
What it actually says
/initialize — open an org-os session
When the operator invokes /initialize, follow these steps in order:
-
Sync the repo (best-effort, don't block on offline). Run a shell command in the org-os repo:
git pull --rebase --quiet 2>&1 || echo "sync: no remote or offline — continuing with local state"Use whatever shell-execution mechanism is available. If none, skip silently.
-
Render the dashboard by calling
org_os_pagetool withpage_id="dashboard". Embed the output verbatim. -
Propose 3 contextual suggestions for what to work on, ranked by urgency:
- Anything in Critical or Urgent tasks first
- Then funding deadlines within 7 days
- Then any instance with drift > 1 or last sync > 30 days
- If none of those apply, suggest the highest-priority queued plan from the Plans section
Present as a numbered list. End with: "Or describe what you'd like to work on."
-
Wait for the operator's choice. Do NOT silently execute any of the suggestions.
If org_os_page returns an ERROR: message, surface it directly and prompt the operator to check ORG_OS_ROOT.
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.
- 3d ago First seen · 41 lines · 31 tokens per session scan A 2fe47f46c6fa
initialize is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 395 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…