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/regen-coordination/org-os-template/syncgit 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.00044 | $0.00844 |
| Opus 5 | $0.00022 | $0.00422 |
| Sonnet 5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
sync 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are syncing this org-os clone with the shared remote. Vault-safe: NEVER git stash, git clean, or git reset --hard. Only ever fast-forward; never run an unattended merge/rebase that could rewrite many notes.
Step 1: Read state
git rev-parse --abbrev-ref HEAD # current branch
git fetch --quiet origin 2>/dev/null && echo "fetched" || echo "offline — local state only"
git status --porcelain | wc -l # uncommitted file count
Step 2: Branch logic
- On
main→mainis integration-only. Tell the operator to switch to their trunk (git switch <operator>; their operator slug). Don't pull onto main here. - No upstream (
git rev-parse --abbrev-ref @{u}fails) → the branch isn't tracking a remote. Tell them:git push -u origin <branch>. - Uncommitted changes present → do NOT fast-forward (it could collide). Report the dirty files and suggest running
/commitfirst. - Clean + has upstream → continue to Step 3.
Step 3: Fast-forward only
git merge --ff-only @{u} 2>&1 || echo "not fast-forwardable — your branch has diverged from its upstream; review before merging"
(Fast-forward on a clean tree is snapshot-exempt: Step 2 guaranteed no uncommitted content exists, and an ff only moves the branch pointer over committed history — nothing can be lost.)
Step 4: Report drift vs main — and offer to pull it in
git rev-list --left-right --count origin/main...HEAD 2>/dev/null | awk '{print "vs origin/main: behind "$1", ahead "$2}'
# If behind, show WHICH shared files main has that this trunk lacks (the actionable part):
git diff --stat HEAD...origin/main -- '*.md' 'data/*.yaml' 'docs/**' 'skills/**' 'packages/**' '.claude/**' 2>/dev/null | tail -12
Report in 2–3 lines: current branch, whether it fast-forwarded, ahead/behind origin/main, and any uncommitted files.
main is the shared consolidation layer — teammates' merged plans, data, and tooling land there, and your trunk does not receive them automatically. Fast-forwarding your trunk (Step 3) only pulls your own pushed history, not main's. So a file a teammate consolidated to main (e.g. a plan doc) will be missing from your trunk until you pull main in — this is the #1 "I don't have that file" gotcha.
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 · 52 lines · 44 tokens per session scan A 61a7f45caec0
sync is a command published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 844 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.