sync

A one-way synchronization workflow that copies selected parts of a live production system to a local development environment. A recipe defines what database, images, feed, or other data can be pulled.

In plain words
What is it for?
Use it to pull production database content, images, feeds, or other mapped data into local paths and review the size of each transferred part.
Why use it?
It helps make local data resemble production while preventing accidental uploads from local development to production. It also shows what local state will be overwritten before syncing.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/artttj/rapid-stack/sync
Any agent
npx skills add artttj/rapid-stack --skill sync
Clone the repo
git clone --depth 1 https://github.com/artttj/rapid-stack

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 154 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.00154
Opus 5 $0.00015 $0.00077
Sonnet 5 $0.00006 $0.00031
Haiku 4.5 $0.00003 $0.00015

Measured yesterday against content hash b4977c8a6c15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

plugins/op/skills/sync/SKILL.md · 15 lines

What it actually says

op:sync

  1. Read recipe sync (a map of part → command). Missing → op:project-recipes discovery.
  2. Arrow-choice which parts to pull (all preselected).
  3. Confirm before overwriting local state — list exactly what gets replaced.
  4. Run each part; a failing part reports and the rest continue.
  5. Hard stop: this command never pushes local state to prod. That is /op:ship's lane.

Proof at end: per part — what moved, its size (du -sh), the local path.

Changes

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.

  1. yesterday First seen · 15 lines · 0 tokens per session scan A b4977c8a6c15

Subscribe to this mod's changes

sync is a skill published in the GitHub repository artttj/rapid-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 154 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.