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/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/sync-disable)<a href="https://agentmods.dev/commands/arpitnath/claude-capsule-kit/sync-disable"><img src="https://agentmods.dev/badge/commands/arpitnath/claude-capsule-kit/sync-disable/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/arpitnath/claude-capsule-kit/sync-disable"><img src="https://agentmods.dev/badge/commands/arpitnath/claude-capsule-kit/sync-disable.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.00006 | $0.00179 |
| Opus 5.5 | $0.00002 | $0.00072 |
| Sonnet 5.5 | $0.00001 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
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 2mo 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
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
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.
- 2mo ago First seen · 36 lines · 6 tokens per session scan A f521e382cc6e
sync-disable is a command published in the GitHub repository arpitnath/claude-capsule-kit (93 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 179 once invoked, about $0.0000 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-30.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
clean
Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
pr
Create a pull request from the current branch.
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.