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/commitnpx skills add regen-coordination/org-os-template --skill commitgit 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.00049 | $0.00553 |
| Opus 5 | $0.00024 | $0.00277 |
| Sonnet 5 | $0.00010 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
commit 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.
What it actually says
You are making a guided commit on this org-os clone. Vault-safe: NEVER git stash, git clean, or git reset --hard.
Step 1: Guard the branch
git rev-parse --abbrev-ref HEAD
If the branch is main: STOP. main is integration-only. Tell the operator to switch to their operator trunk first: git switch <operator> (their operator slug), or create it with bash scripts/operator-setup.sh <operator>. Do not commit to main.
Step 2: Show what will be committed
git status
git diff --stat
Summarize the changes in plain language. If clearly-unrelated changes are bundled in (e.g. someone else's in-progress work), flag it and offer to stage selectively instead of git add -A — don't absorb another operator's scope into this commit.
Step 3: Stage + commit
git add -A # or stage selectively per Step 2
Write a conventional commit message — type(scope): summary — that describes the real change. Types: feat, fix, docs, session, data, design, chore. Then:
git commit -m "<message>"
Step 4: Push
git push 2>&1 || echo "push failed — if 'no upstream', run: git push -u origin $(git rev-parse --abbrev-ref HEAD)"
If push fails on auth/permissions, report it plainly (the operator may need write access to the repo).
Step 5: Report
One line: what was committed (short hash + summary) and whether it pushed. If the commit touched shared structural files (data/*.yaml, HEARTBEAT.md, MEMORY.md, federation.yaml, scripts/, .well-known/, docs/plans/), remind: these are PR-gated — open a PR to main (or flag for the weekly merge-consolidation) rather than expecting them to auto-promote.
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 · 50 lines · 49 tokens per session scan A 0aedb8b74353
commit is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 553 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…