Borrowing it
Nothing to install: this file belongs to Koroqe/OPOS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Koroqe/OPOS/main/.claude/skills/auto-sync/SKILL.mdgit clone --depth 1 https://github.com/Koroqe/OPOSWrote 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/koroqe/opos/auto-sync)<a href="https://agentmods.dev/skills/koroqe/opos/auto-sync"><img src="https://agentmods.dev/badge/skills/koroqe/opos/auto-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/koroqe/opos/auto-sync"><img src="https://agentmods.dev/badge/skills/koroqe/opos/auto-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.00042 | $0.06461 |
| Opus 5.5 | $0.00017 | $0.02584 |
| Sonnet 5.5 | $0.00008 | $0.01292 |
| Haiku 4.5 | $0.00004 | $0.00646 |
Grade A, and why
auto-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 yesterday.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
auto-sync
When to use
As a scheduled routine (registered via /schedule-process auto-sync, daily cron 17 6 * * *) — the autonomous counterpart of sync-from-core. Also manually invokable as /auto-sync (e.g. to test the flow, or to pull an update immediately without the interactive review sync-from-core provides), or as /auto-sync --dry_run to see what a run would do without mutating anything.
The contract difference from sync-from-core is deliberate and absolute: sync-from-core waits for a human to review and commit; auto-sync commits clean syncs itself and escalates only when something needs a human. One skill cannot carry both postures — do not merge them.
Authority mapping
The scheduled-run prelude instructs: refuse any action not in the declared authority list. For this skill the declared list [commit, push, file_issue] maps to concrete actions as follows — every action below is inside the declaration:
- commit — the full local mutation set needed to produce the sync commit: creating/deleting
opos-auto-sync-<tag>work branches, the file writes performed bycopier update, the CHANGELOG-only.rejauto-resolution (including deletingCHANGELOG.md.rej), refreshing.claude/.last-update-check, ff-merging the work branch to the default branch, and writing the run record. - push —
git pushof the ff-merged default branch, and of the work branch on the conflict path. On thecloudruntime, when the direct push is refused, the fallback ofshared/cloud-integration.md(push the session'sclaude/*branch, open and merge a PR via REST) is the same integration act undercommit+push; it needs no additional authority entry. - file_issue —
gh issue createin the consumer's own repo (conflict, divergence, push-failure, and Action-mutual-exclusion escalations).
Anything outside this mapping (e.g. hand-editing files beyond the CHANGELOG rule, force-pushing, touching unrelated branches, writing to any other repo) is outside the declaration — refuse and record the refusal.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +3 lines 774a883be17b
- 27d ago Changed · +3 lines 74c4ad5827b5
- 28d ago Changed · +16 lines 9003dfaf9efe
- 1mo ago Changed · +11 lines 45abc3bce10c
- 1mo ago First seen · 98 lines · 42 tokens per session scan A dbf661c6a56d
auto-sync is a skill published in the GitHub repository Koroqe/OPOS (4 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 6,461 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 skills, from other repositories
git-commit-integrity
Ensures every commit in a series is what it claims to be — a working, gate-passing snapshot in isolation, not just a slice of a working directory that happened to pass while other changes sat nearby. Covers verifying commit history after the fact, designing pre-commit hooks that check the commit rather than the…
workflow-solo
Single-agent feature pipeline with adaptive complexity. User-invoked entry point via /workflow-solo; not for autonomous or subagent use.
summarize-change-log
Condense long commit logs, squash messages, or change narratives into 1–5 GitHub-ready markdown bullets with Conventional Commit subjects (≤50 chars). Use when the user asks to summarize a git log, boil down commits, write a squash-merge message, or produce a five-bullet PR/merge summary.
pr-address-comments-all
Address GitHub PR review comments on one or more PRs in parallel, each in its own git worktree on the PR's branch, reusing the pr-address-comments procedure. Auto-starts (look up PRs, create worktrees, fetch comments), then pauses to show a per-PR addressing plan for approval; after approval each PR is handled by a…
sidecar
Use the sidecarsync CLI to read, update, and synchronize Sidecar notes or state in repos with .sidecar configurations. Covers peer selection, standalone repos, per-file rules, and fork recovery.
delivery
Fecha o ciclo de entrega local — build check, bump semântico, changelog e commit convencional. Deploy remoto somente sob a condição dupla do Ops. Use para "finalizar tarefa", "fazer release" ou "publicar versão".