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 regen-coordination/org-os-template --skill hermes-integrationgit clone --depth 1 https://github.com/regen-coordination/org-os-templateWrote 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/regen-coordination/org-os-template/hermes-integration)<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/hermes-integration"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/hermes-integration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/hermes-integration"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/hermes-integration.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.00661 |
| Opus 5 | $0.00023 | $0.00331 |
| Sonnet 5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
org_os_pages 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
org_os_pages — view org-os state from hermes
This skill registers the org_os_page tool, which calls npm run page <id> in the operator's org-os workspace and returns the rendered text. Hermes can use this tool whenever the operator asks about organizational state — projects, tasks, instances, plans, decisions, federation health, and so on.
Usage
In a hermes conversation, ask:
- "Show me the org-os dashboard" →
org_os_page("dashboard") - "What's on this week?" →
org_os_page("this-week") - "Drill into v2-stabilization" →
org_os_page("project/v2-stabilization") - "Are any instances drifting?" →
org_os_page("health") - "What decisions did we make recently?" →
org_os_page("decisions")
The tool's output is markdown-clean — embed it inline in your response.
Page ids
The full list lives in packages/tui-data/src/builtin-pages.mjs of the org-os repo. Common ids:
- Section:
dashboard,projects,tasks,plans,instances,federation,members,ideas,funding,calendar,memory,decisions,skills,packages - Entity:
project/<id>,instance/<id>,plan/<id>,idea/<id>,member/<id>,skill/<id>,package/<id>,decision/<slug> - Cross-cut:
health,this-week,promotions,attention
Setup
Set ORG_OS_ROOT in the operator's shell to point at the org-os repo:
export ORG_OS_ROOT=~/code/org-os
If ORG_OS_ROOT is not set or doesn't point at a directory containing package.json, the tool returns an actionable error rather than crashing.
When to use this skill
Trigger when the operator asks anything about:
- Project status, workstream stages, owners, dates
- Open tasks, urgent or critical items
- Plan pipeline (scoping/queued/active/completed)
- Federation health: instances, drift, last-sync
- Recent decisions and their rationale
- Funding deadlines or calendar events this week
- Skills or packages eligible for promotion
- "What needs my attention?" — use
attentionpage
Don't use for general code exploration — this is org-state observability, not file search.
What ships with it
7 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.
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 · 64 lines · 46 tokens per session scan A b455824945c1
org_os_pages is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 661 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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.