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 commands/leoyang183/sync-agents-settings/syncgit clone --depth 1 https://github.com/Leoyang183/sync-agents-settingsWhat 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.00045 | $0.00606 |
| Opus 5 | $0.00023 | $0.00303 |
| Sonnet 5 | $0.00009 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00061 |
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 2d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync MCP server settings from Claude Code to other AI coding agents.
Arguments
The user may pass target names after the command: /sync gemini codex
If no targets specified, sync to all targets (gemini, codex, opencode, kiro, cursor, kimi, vibe, qwen, amp, cline, windsurf).
The user may also pass server names to sync only specific servers: /sync --server context7 supabase
The user may also pass flags:
--server <names...>or-s <names...>— sync only specified MCP servers by name--skip-oauth— skip MCP servers that require OAuth authentication--no-backup— skip creating backup of target config files--codex-home <path>— custom Codex config directory--kimi-home <path>— custom Kimi config directory--vibe-home <path>— custom Vibe config directory--qwen-home <path>— custom Qwen Code config directory--amp-home <path>— custom Amp config directory--cline-home <path>— custom Cline CLI config directory--windsurf-home <path>— custom Windsurf config directory--report json— output machine-readable JSON summary (CI-friendly)
Execution Flow
-
Parse targets and server names from user arguments. Build the command:
npx sync-agents-settings sync --dry-run --target <targets>Add--server <names>if the user specified specific servers. Add--skip-oauthor--no-backupif the user specified them. -
Run the dry-run command using bash. This previews what will change without writing files.
-
Present the results to the user:
- Servers that will be added to each target
- Servers that will be skipped (already exist or unsupported)
- If all servers are skipped, inform the user and stop here.
-
Ask the user: "Proceed with sync?"
-
If confirmed, run the same command without
--dry-run:npx sync-agents-settings sync --target <targets> -
Present the final results.
- If
--report jsonis used, return raw JSON and avoid text post-processing.
- If
Error Handling
- If
npxfails with "command not found" or network error: suggestnpm install -g sync-agents-settingsas fallback. - If the CLI exits with non-zero code: show the stderr output and suggest checking that target agent directories exist.
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.
- 2d ago First seen · 54 lines · 45 tokens per session scan A daa3405b102c
sync is a command published in the GitHub repository Leoyang183/sync-agents-settings (8 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 606 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 commands, from other repositories
anti-pattern-czar
You are the Anti-Pattern Czar, an expert at identifying and fixing error handling anti-patterns.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
om-dump
Freeform capture mode. Dump anything — conversations, decisions, incidents, wins, thoughts — and I'll route it all to the right notes with proper templates, frontmatter, and wikilinks.
maintainer
Meta-skill that loads all llmwiki governance docs and exposes the three maintainer slash commands.
release
Walk the llmwiki release process step by step.
wiki-synthesize
Synthesize wiki/sources/ .md pages from raw session transcripts using the configured LLM backend.