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.
git 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-validate)<a href="https://agentmods.dev/commands/leoyang183/sync-agents-settings/sync-validate"><img src="https://agentmods.dev/badge/commands/leoyang183/sync-agents-settings/sync-validate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/leoyang183/sync-agents-settings/sync-validate"><img src="https://agentmods.dev/badge/commands/leoyang183/sync-agents-settings/sync-validate.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00484 |
| Opus 5.5 | $0.00006 | $0.00194 |
| Sonnet 5.5 | $0.00003 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
sync-validate 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 1mo 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.
What it actually says
Validate MCP server definitions from Claude Code against target agent capabilities.
Arguments
The user may pass target names: /sync-validate codex opencode
If no targets are specified, validate all targets (gemini, codex, opencode, kiro, cursor, kimi, vibe, qwen, amp, cline, windsurf).
Optional flags:
--skip-oauth— ignore OAuth-only servers from validation--fix— after validation passes, auto-run reconcile--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 validate --target <targets>Add--skip-oauthif requested. - Present issues grouped by target:
errorissues: invalid schema that cannot be converted safelywarningissues: lossy conversion risk or manual setup neededcommand/urlwith blank-only values are treated as missing and reported aserror- OAuth-only servers emit
OAUTH_MANUAL_SETUP_REQUIREDwarning only (no duplicate transport-field errors)
- If errors exist, tell the user to fix them before running
/sync. - If only warnings exist, allow user to proceed based on risk tolerance.
- If
--fixis provided and no validation errors exist, run reconcile automatically.- If no drift is found, return a noop result ("Nothing to fix") instead of reporting reconcile success.
Error Handling
- Exit code
2means validation errors were found. - Exit code
0means no errors (warnings may still exist). - 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 validate (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.
- 1mo ago First seen · 43 lines · 14 tokens per session scan A a88c64c44cbd
sync-validate is a command published in the GitHub repository Leoyang183/sync-agents-settings (7 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 484 once invoked, about $0.0001 per session on Opus 5.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
secrets
Provides tools for managing environment variables and secrets for your Supabase project.
stop
Stops the Supabase local development stack.
session-stop
Stop recording and save this agent session to the project ledger.
setup_research_plan
Set up or start a research project.
tasks
Generate atomic task files in tasks/ directory with index.md and traceability.md (Atomic Traceability Model).
checklist
Generate a custom checklist for the current feature based on user requirements.