A synchronization tool for an existing Trabuco project's AI-tooling files, such as skills, subagents, prompts, hooks and review setup. It compares the project with what the installed Trabuco CLI would currently generate.

It is for checking which AI-tooling files would be added, reviewing the proposed changes in a dry run, and applying those additions after confirmation. It first verifies that the directory is a Trabuco project.

It identifies missing files without changing files that are already present, so a project can catch up with the CLI's tooling safely and additively.

sync — Skill for Claude Code and Codex by arianlopezc: A synchronization tool for an existing Trabuco project's AI-tooling…

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/arianlopezc/trabuco/sync

Any agent

npx skills add arianlopezc/Trabuco --skill sync

Clone the repo

git clone --depth 1 https://github.com/arianlopezc/Trabuco

Made for: Claude Code, Codex.

Or install trabuco, the plugin that ships this one along with the rest of its 10 skills, 24 agents, 2 hooks, 1 MCP server.

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/arianlopezc/trabuco/sync.svg)](https://agentmods.dev/skills/arianlopezc/trabuco/sync)

Your own site

<a href="https://agentmods.dev/skills/arianlopezc/trabuco/sync"><img src="https://agentmods.dev/badge/skills/arianlopezc/trabuco/sync.svg" alt="Measured on agentmods" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 867 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.

Model	Per session	Once invoked
Fable 5	$0.00048	$0.00867
Opus 5	$0.00024	$0.00434
Sonnet 5	$0.00010	$0.00173
Haiku 4.5	$0.00005	$0.00087

Measured 3d ago against content hash adef1dab054d, 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 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.

plugin/skills/sync/SKILL.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sync AI tooling in a Trabuco project

This skill updates the AI-tooling layer of an existing Trabuco project so its skills, subagents, prompts, hooks, and review scaffolding match what the currently-installed Trabuco CLI would generate today.

Flow

Identify the project. If the user didn't provide a path, use the current working directory. Call mcp__trabuco__get_project_info to confirm it's a Trabuco project — if it returns an error, tell the user and stop.
Dry-run first. Call mcp__trabuco__sync_project with apply: false to produce a plan. The response is JSON with:
- would_add: files the current CLI would emit that are missing
- already_present: files that exist (untouched regardless of content)
- out_of_jurisdiction: business / infra files sync never considers
- blockers: reasons sync can't proceed (e.g., no .trabuco.json)
Summarize to the user. Present the would_add list grouped by directory (.claude/, .codex/, .cursor/, .github/, .ai/, top-level). Keep the explanation short — the plan output speaks for itself.
Confirm. If would_add is non-empty, ask the user "Apply these N additions?" Wait for explicit confirmation (not just acknowledgement — "yes" or "apply", not "sounds good").
Apply. On confirmation, call mcp__trabuco__sync_project with apply: true. Report the count of files added.
Next steps. Tell the user:
- "Restart your Claude Code session if you want the new hooks and skills to load immediately."
- "Run trabuco doctor to confirm project health."
- "Review the changes with git diff before committing."

Rules

Never skip the dry-run. The user should always see what's going to happen before it happens.
If would_add is empty, report that clearly ("AI tooling is already up to date") and stop — no need to confirm or apply.
If there are blockers, surface them verbatim and suggest fixes (usually: make sure the directory is a Trabuco project with .trabuco.json).
Never claim sync modified existing files. It doesn't. If the user asks about refreshing a specific existing file (like CLAUDE.md), explain that sync is additive-only and the workaround is to delete the file first, then run sync.
Don't imply sync touches business code. Sync has strict jurisdiction boundaries: Java source, POMs, application.yml, docker-compose.yml, migrations, and CI workflows (other than copilot-setup-steps.yml) are never considered. If the user asks sync to "update my application.yml," redirect them.

Read the full file on GitHub · 55 lines

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.

3d ago First seen · 55 lines · 48 tokens per session scan A adef1dab054d

Subscribe to this mod's changes

sync is a skill published in the GitHub repository arianlopezc/Trabuco (0 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 867 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.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens