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 skills/koroqe/opos/auto-syncnpx skills add Koroqe/OPOS --skill auto-syncgit 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.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 | $0.00042 | $0.04062 |
| Opus 5 | $0.00021 | $0.02031 |
| Sonnet 5 | $0.00008 | $0.00812 |
| Haiku 4.5 | $0.00004 | $0.00406 |
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 3d 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.
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. - 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.
Inputs
dry_run(optional bool; default false): probe and print what would happen; mutate nothing (no branch, no cache write, no run record).target_version(optional; default: latest non-prerelease release tag from upstream). Must match^v?[0-9]+\.[0-9]+\.[0-9]+$— reject anything else before use (the value is interpolated into--vcs-refand a branch name).
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.
- 3d ago First seen · 98 lines · 42 tokens per session scan A dbf661c6a56d
auto-sync is a skill published in the GitHub repository Koroqe/OPOS (2 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 4,062 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 skills, from other repositories
commit
Stage and commit git changes with conventional prefixes. Use when the user asks to commit, save changes, write a commit message, or push staged work to the repository.
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".
speckit-git-commit
Auto-commit changes after a Spec Kit command completes.
speckit-git-initialize
Initialize a Git repository with an initial commit.
super-evolve
Ultimate self-evolution skill. Merges evolve + self-improve into one comprehensive meta-skill with external research, area focus, dry-run mode, and expanded memory mining.
pr-to-video
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR…