sync-disable

A command that turns off automatic Claude Code session syncing to GitHub. Existing synced sessions stay in GitHub, and the saved sync settings remain available.

In plain words
What is it for?
Use it when you want to pause session backups or stop cross-device continuation without deleting existing synced sessions.
Why use it?
It stops new sessions from syncing while keeping your previous session data and configuration intact. Syncing can be enabled again later.

Command

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 commands/arpitnath/claude-capsule-kit/sync-disable
Clone the repo
git clone --depth 1 https://github.com/arpitnath/claude-capsule-kit
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 179 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00006 $0.00179
Opus 5 $0.00003 $0.00089
Sonnet 5 $0.00001 $0.00036
Haiku 4.5 $0.00001 $0.00018

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

Security

Grade A, and why

sync-disable 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.

commands/sync-disable.md · 36 lines

What it actually says

Disable Session Sync

Turn off automatic session syncing to GitHub.

Disable Sync

python3 -c "
import json
import os

config_file = '.claude/sync-config.json'
if os.path.exists(config_file):
    with open(config_file) as f:
        config = json.load(f)
    config['enabled'] = False
    with open(config_file, 'w') as f:
        json.dump(config, f, indent=2)
    print('✓ Session sync disabled')
    print('  Re-enable anytime with /sync-enable')
else:
    print('Session sync was not configured')
"

Notes

  • Your existing synced sessions remain on GitHub
  • The sync config is preserved (just disabled)
  • Re-enable anytime with /sync-enable
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. 3d ago First seen · 36 lines · 6 tokens per session scan A f521e382cc6e

Subscribe to this mod's changes

sync-disable is a command published in the GitHub repository arpitnath/claude-capsule-kit (88 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 179 once invoked, about $0.0000 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-30.