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 mishahanin/heading-os --skill syncgit clone --depth 1 https://github.com/mishahanin/heading-osWrote 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/mishahanin/heading-os/sync)<a href="https://agentmods.dev/skills/mishahanin/heading-os/sync"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/sync/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/mishahanin/heading-os/sync"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/sync.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.00033 | $0.01161 |
| Opus 5 | $0.00016 | $0.00580 |
| Sonnet 5 | $0.00007 | $0.00232 |
| Haiku 4.5 | $0.00003 | $0.00116 |
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 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Sync
Manually sync the workspace using plain git. This replaced the retired
workspace-sync.py mechanism on 2026-06-26. There is no longer a
copy-and-orphan-delete engine, no scheduled sync task, and no risk of the old
"delete the engine tree" failure. Sync is now two simple, non-destructive
operations.
What Gets Synced
- Pull (code + data) -
git pull --ff-onlyon the engine clone (.heading-os) and the data overlay (.heading-os-data). Fast-forward only, so a divergent local history surfaces as a plain error instead of an implicit merge. 1b. Corporate content (execs) -python scripts/sync-corporate.pyrefreshes the gitignored.corporate-repo/clone ofheading-os-corporate, read in place viaget_corporate_root(). It self-no-ops on the CEO workspace, so it runs unconditionally in the pull sequence (no skill-level branch). - Backup (push) -
python scripts/push-all.pycommits and pushes BOTH repos to their privateorigin/main. That push runs the pre-push secret scan and the[0 0]ahead/behind verification.
First-run record recovery after a clean deploy is a separate one-shot:
python scripts/import-legacy-records.py --from <old-records-path>(local, non-destructive). It is NOT part of /sync.
Options
/sync- pull, then backup/sync pull-git pull --ff-onlyon the engine and data clones only/sync backup-python scripts/push-all.pyonly
Steps
- Resolve the engine root (the workspace you launched from) and the data root
(the
.heading-os-datasibling, orHEADING_OS_DATAif set). - For pull: run
git -C <engine-root> pull --ff-onlyandgit -C <data-root> pull --ff-only, thenpython scripts/sync-corporate.py(refreshes.corporate-repo/on execs; no-ops on the CEO workspace). Show each result. - For backup: run
python scripts/push-all.pyand show its output. - For bare
/sync: run the pull sequence first. - Then run the backup.
- If a step fails, explain plainly and suggest a fix:
git pullnon-fast-forward: "Local history diverged - reconcile manually (git -C <root> status) before syncing; /sync will not force or merge."- push-all secret-scan refusal: "A tracked file looks like it holds a secret -
move it to
.envand retry; never pass--no-verify." - push-all exit
3: NOT a failure. At least one repository was skipped (a branch that is notmain, an unarmed engine test gate). Every skipped repo is still committed locally. Read its headline:Partial: N of Mmeans the rest pushed and verified;NOTHING PUSHED: all Mmeans no new off-machine copy exists. Report the shape, name the repo, quote the reason. Full guidance:/backupSKILL.md. - Git auth: "GH_TOKEN missing or expired - check the engine
.env."
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 · 98 lines · 33 tokens per session scan A 3b1acab24d6c
sync is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,161 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-09-03.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.