claude-code-sync CLAUDE.md

Project instructions for Claude Code Sync, a Bash command-line tool that backs up, restores, and synchronizes Claude Code settings between Ubuntu computers.

In plain words
What is it for?
Use them when maintaining encrypted backups, Git or SSH synchronization, restore operations, snapshots, or conflict handling.
Why use it?
They document the supported platforms, encryption, sync methods, dependencies, repository structure, and development rules.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/btafoya/claude-code-sync/claude-md
Clone the repo
git clone --depth 1 https://github.com/btafoya/claude-code-sync
Per session 3,381 This file is loaded in full into every session.
When invoked 3,381 The same file — it is already loaded in full.
Security scan D 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.03381 $0.03381
Opus 5 $0.01690 $0.01690
Sonnet 5 $0.00676 $0.00676
Haiku 4.5 $0.00338 $0.00338

Measured 2d ago against content hash 90224846614b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

claude-code-sync CLAUDE.md scanned grade D with 2 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

chmod 700 ~/.claude-code-sync # Owner only

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- ✅ Use trap for cleanup: `trap 'rm -rf "$TMP_DIR"' EXIT`
CLAUDE.md · 553 lines

How it starts

The opening of the file, as written. The whole thing — 553 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Project-specific guidance for Claude Code when working on the claude-code-sync repository.


Project Overview

claude-code-sync is a CLI utility for backing up, restoring, and synchronizing Claude Code configurations across multiple Ubuntu machines. The tool provides encrypted backups, multiple sync strategies (git, manual, SSH direct), and intelligent conflict resolution.

Key Technologies

  • Language: Bash (v4.0+)
  • Platform: Ubuntu (all flavors)
  • Encryption: GPG (AES-256-GCM)
  • Sync Backends: Git, SSH/rsync, local filesystem
  • Dependencies: gpg, tar, gzip, sha256sum, jq, rsync, git

Project Structure

claude-code-sync/
├── bin/
│   └── claude-code-sync              # Main CLI executable
├── lib/
│   ├── utils.sh                # Logging, utilities, helpers
│   ├── encryption.sh           # Encryption/decryption engine
│   ├── backup.sh               # Backup operations
│   ├── restore.sh              # Restore operations
│   ├── conflict.sh             # Conflict detection/resolution
│   ├── snapshot.sh             # Snapshot management
│   ├── sync.sh                 # Synchronization logic
│   └── storage.sh              # Storage backend abstraction
├── config/
│   └── default.conf            # Default configuration template
├── docs/
│   └── [user documentation]
├── tests/
│   └── [test suite]
└── claudedocs/
    ├── PROJECT_SPECIFICATION.md       # Complete requirements
    ├── ARCHITECTURE.md                # System design
    ├── IMPLEMENTATION_ROADMAP.md      # Implementation guide
    └── QUICK_START.md                # Getting started

Development Guidelines

Code Style

Bash Best Practices:

  • Use set -euo pipefail at the start of all scripts
  • Always quote variables: "$variable"
  • Use readonly for constants
  • Prefer functions over inline code
  • Use descriptive function and variable names

Naming Conventions:

  • Functions: snake_case (e.g., backup_full, encrypt_file)
  • Variables: snake_case (e.g., backup_dir, encrypted_file)
  • Constants: UPPER_SNAKE_CASE (e.g., CIPHER_ALGO, SYNC_DIR)
  • Private functions: prefix with _ (e.g., _internal_helper)

Read the full file on GitHub · 553 lines

Changes

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.

  1. 2d ago First seen · 553 lines · 3,381 tokens per session scan D 90224846614b

Subscribe to this mod's changes

claude-code-sync CLAUDE.md is an instructions file published in the GitHub repository btafoya/claude-code-sync (2 stars, last pushed 10mo ago), licensed MIT. It adds 3,381 tokens to every session, about $0.0169 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.