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-listgit 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.00016 | $0.00137 |
| Opus 5 | $0.00008 | $0.00068 |
| Sonnet 5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
sync-list 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.
What it actually says
List all MCP servers that Claude Code knows about.
Execution Flow
-
Run:
npx sync-agents-settings list -
Present the output to the user in a readable format:
- Group servers by transport type (STDIO, HTTP, SSE)
- Show the source of each server (config = from ~/.claude.json, plugin = from Claude plugin)
- Highlight any servers that require OAuth authentication
Error Handling
- If
npxfails: suggestnpm install -g sync-agents-settingsas fallback.
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 · 20 lines · 16 tokens per session scan A fbbe77bfc54d
sync-list is a command published in the GitHub repository Leoyang183/sync-agents-settings (8 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 137 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-tidy
Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits oversized notes, reports stale open loops, fixes links. Safe by construction: never deletes, never commits, zero content loss.
ox-session-review
Command "ox-session-review" from sageox/ox, covering failure-mode watch-list (read first), from the ledger root. should print 0, phase 1 — scan & score (read-only), quality buckets (first match wins) and removal candidates.
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-init
Scaffold an empty llmwiki — create raw/, wiki/, site/ directories and seed wiki/index.md, wiki/log.md, wiki/overview.md.