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 handoffgit 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/handoff)<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/handoff"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/handoff.svg" alt="Measured on agentmods" 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.00064 | $0.00752 |
| Opus 5 | $0.00032 | $0.00376 |
| Sonnet 5 | $0.00013 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
handoff 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 7d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are generating a handoff prompt — a compact, copy-paste brief another operator pastes into THEIR clone of this org-os instance (any agent/editor) to pick up a piece of work. It self-syncs their trunk with plain git (no dependency on /sync existing), points them at the target, and ends with a clean trunk→main PR.
The output is the deliverable. Keep it minimal.
Step 1: Parse the ask
$ARGUMENTS = <operator> <target> [the ask…]
- operator → trunk: resolve the operator's trunk slug from the instance's operator roster (
data/members.yaml, or the trunk branches on the remote:git branch -r). If ambiguous, ask which trunk. - target: a repo doc (
docs/SOME-DOC.mdor a bare filename, optionally a§N/heading) or a task id (task-…, resolve fromdata/tasks.yaml). - the ask: the rest — one clause naming the concrete deliverable. If absent, infer from the target; if still unclear, ask ONE question. Don't over-ask.
Step 2: Resolve link + trunk
- Live link: derive the repo's web URL from
git remote get-url origin→https://github.com/<org>/<repo>/blob/main/<docpath>(append#<anchor>only if confident it resolves; otherwise name the section inside the ask). For a task, link the same repo path todata/tasks.yamland cite the id. - Confirm the trunk slug from Step 1.
Step 3: Emit the prompt (a single paragraph the operator pastes into their instance)
The prompt is an instruction to THEIR agent (Claude Code / OpenCode / Cursor / Zed) — natural language; the agent does the git sync, the edits, and the PR. Output ONLY this filled template in a code block, nothing else:
In <REPO-NAME>: sync my `<TRUNK>` trunk with `main` — fetch, switch to <TRUNK>, merge `origin/main` (fast-forward if possible, else a merge commit), push. Then open <LINK> and <ASK>. Commit to <TRUNK> and open a PR to `main`.
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.
- 7d ago First seen · 38 lines · 64 tokens per session scan A 8ec901cecf1c
handoff is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 752 once invoked, about $0.0003 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…