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.
git 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/commands/regen-coordination/org-os-template/commit)<a href="https://agentmods.dev/commands/regen-coordination/org-os-template/commit"><img src="https://agentmods.dev/badge/commands/regen-coordination/org-os-template/commit/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/commands/regen-coordination/org-os-template/commit"><img src="https://agentmods.dev/badge/commands/regen-coordination/org-os-template/commit.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.00047 | $0.00518 |
| Opus 5.5 | $0.00019 | $0.00207 |
| Sonnet 5.5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
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 1mo 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.
$ARGUMENTS
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.
- 1mo ago First seen · 49 lines · 47 tokens per session scan A af692f8b0bb0
commit is a command published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 518 once invoked, about $0.0002 per session on Opus 5.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
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.