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 instructions/leoyang183/sync-agents-settings/claude-mdgit 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/instructions/leoyang183/sync-agents-settings/claude-md)<a href="https://agentmods.dev/instructions/leoyang183/sync-agents-settings/claude-md"><img src="https://agentmods.dev/badge/instructions/leoyang183/sync-agents-settings/claude-md.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.01539 | $0.01539 |
| Opus 5 | $0.00770 | $0.00770 |
| Sonnet 5 | $0.00308 | $0.00308 |
| Haiku 4.5 | $0.00154 | $0.00154 |
Grade A, and why
sync-agents-settings CLAUDE.md 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Commands
pnpm build # Compile TypeScript (src/ → dist/)
pnpm test # Run all tests (vitest)
pnpm test:coverage # Run tests with v8 coverage report
pnpm lint # ESLint check
pnpm format:check # Prettier check
pnpm format # Prettier auto-fix
pnpm dev list # Run CLI from source (tsx)
pnpm dev doctor # Check MCP drift from source without writing files
pnpm dev validate # Validate schema/capability compatibility before syncing
pnpm dev reconcile # Run validate + doctor + sync missing in one flow
pnpm dev doctor -- --fix --dry-run # Auto-fix drift via reconcile (preview)
pnpm dev reconcile -- --report json # Machine-readable output for CI integration
pnpm dev sync -- --report json --dry-run # Machine-readable sync preview
pnpm dev sync-instructions -- --report json --dry-run --global --target gemini # Machine-readable instruction sync preview
pnpm dev diff -- --report json --target gemini codex # Machine-readable diff output
pnpm dev report-schema -- --write docs/report-schema.md # Regenerate report schema markdown from code
pnpm dev report-schema -- --check # CI check for stale/missing report schema doc
bash ci-local.sh # Run full local CI (format + lint + typecheck + build + test)
Run a single test file:
npx vitest run src/__tests__/codex-writer.test.ts
Important: Always run bash ci-local.sh before committing to catch lint/format/type errors early.
Architecture
This is a CLI tool that reads MCP server configurations from Claude Code and writes them to other AI coding agents in their native formats.
Data flow:
Reader (src/reader.ts)
→ reads ~/.claude.json + enabled plugin .mcp.json files
→ produces UnifiedMcpServer[]
Writers (src/writers/*.ts)
→ each writer converts UnifiedMcpServer[] to target-specific format
→ writes to target config file
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 · 104 lines · 1,539 tokens per session scan A 8fd889b3fac8
sync-agents-settings CLAUDE.md is an instructions file published in the GitHub repository Leoyang183/sync-agents-settings (8 stars, last pushed 5mo ago), licensed MIT. It adds 1,539 tokens to every session, about $0.0077 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 instructions, from other repositories
TokenTracker CLAUDE.md
Claude Code instructions for xiufengsun/TokenTracker, covering claude.md, project shape, frequently used commands, what's where and load-bearing conventions.
TokenTracker AGENTS.md
AGENTS.md instructions for xiufengsun/TokenTracker, covering agent instructions and insforge backend.
turnbreak AGENTS.md
AGENTS.md instructions for Milkeles/turnbreak, covering agent instructions file: turnbreak, 1. project overview, 2. commands, 3. code style and 4. repository conventions.
IDE-Adapter CLAUDE.md
Instructions for godstale/IDE-Adapter, covering claude.md, commands, architecture, adding a new handler and protocol rules.
IDE-Adapter GEMINI.md
Instructions for godstale/IDE-Adapter, covering gemini.md, project overview, building and running and development conventions.
agent-recall CLAUDE.md
Claude Code instructions for d-wwei/agent-recall, covering agent recall: ai development instructions, architecture, privacy tags, build commands and configuration.