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/sync-doctorgit clone --depth 1 https://github.com/Leoyang183/sync-agents-settingsWrote 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/commands/leoyang183/sync-agents-settings/sync-doctor)<a href="https://agentmods.dev/commands/leoyang183/sync-agents-settings/sync-doctor"><img src="https://agentmods.dev/badge/commands/leoyang183/sync-agents-settings/sync-doctor.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.00018 | $0.00624 |
| Opus 5 | $0.00009 | $0.00312 |
| Sonnet 5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
sync-doctor 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 5d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check whether target MCP configs are in sync with Claude Code, without writing any files.
Arguments
The user may pass target names: /sync-doctor gemini codex
If no targets specified, check all targets (gemini, codex, opencode, kiro, cursor, kimi, vibe, qwen, amp, cline, windsurf).
Optional flags:
--skip-oauth— ignore OAuth-only servers from Claude source--codex-home <path>— check project-level Codex config (e.g../.codex)--kimi-home <path>— check project-level Kimi config (e.g../.kimi)--vibe-home <path>— check project-level Vibe config (e.g../.vibe)--qwen-home <path>— check project-level Qwen Code config--amp-home <path>— check project-level Amp config--cline-home <path>— check project-level Cline CLI config--windsurf-home <path>— check project-level Windsurf config--fix— if drift exists, auto-run reconcile to add missing servers--dry-run— with--fix, preview only--no-backup— with--fix, skip backup before writing--report json— emit machine-readable JSON report
Execution Flow
- Parse targets and flags from user arguments.
- Run:
npx sync-agents-settings doctor --target <targets>Add--skip-oauth/--codex-home/--kimi-home/--vibe-home/--qwen-home/--amp-home/--cline-home/--windsurf-homewhen specified. - Present results per target:
No driftwhen fully in syncMissing in <target>when Claude has servers not present in targetExtra in <target>when target has servers absent in ClaudeUnavailableif target directory is missingParse errorwhen target config is malformed
- If drift exists, suggest running
/syncto reconcile.- Or run
/sync-doctor --fixto reconcile automatically.
- Or run
Error Handling
- Exit code
1means drift detected. - Exit code
2means config parse error detected. - With
--fix, failure reasons are specific: parse-related (target config parse error) or validation-related (validation errors detected) before exiting2. - If
npxfails: suggestnpm install -g sync-agents-settingsas fallback. --report jsoncannot be used with--fixon doctor (usereconcile --report jsoninstead).
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.
- 5d ago First seen · 49 lines · 18 tokens per session scan A 0d4ae08ba762
sync-doctor is a command published in the GitHub repository Leoyang183/sync-agents-settings (8 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 624 once invoked, about $0.0001 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.
init
Initialize configurations for Supabase local development.
secrets
Provides tools for managing environment variables and secrets for your Supabase project.
stop
Stops the Supabase local development stack.