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 skills/rohithzr/claudebase/sync-pushnpx skills add rohithzr/claudebase --skill sync-pushgit clone --depth 1 https://github.com/rohithzr/claudebaseWrote 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/skills/rohithzr/claudebase/sync-push)<a href="https://agentmods.dev/skills/rohithzr/claudebase/sync-push"><img src="https://agentmods.dev/badge/skills/rohithzr/claudebase/sync-push.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.00026 | $0.00466 |
| Opus 5 | $0.00013 | $0.00233 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade B, and why
sync-push scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `~/.claude/settings.json` (global settings, opt-in via `--include-global`) What it actually says
Config Sync Push
Push your current local Claude Code configuration to the GitHub backup repo.
What gets pushed
All syncable files from the current project and global config:
.mcp.json,.claude/settings.json.claude/agents/,.claude/commands/,.claude/skills/.claude/hooks/(scripts, config, sounds).claude/rules/,.claude/agent-memory/.auto-memory/(memory files)~/.claude/settings.json(global settings, opt-in via--include-global)
Files that are never pushed: CLAUDE.md (version-controlled with project), settings.local.json, hooks-config.local.json, conversations, sessions.
Instructions
Parse user arguments and run the push script:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync-push.sh" [OPTIONS]
Options:
--profile NAME— Push to a specific profile (default: active profile)--force— Skip multi-machine safety check and secret warnings--dry-run— Show what would be pushed without actually pushing--include-global— Also push~/.claude/settings.json(global settings are opt-in)
Multi-machine warning
If the script warns about another machine having pushed more recently, advise the user to pull first (/sync-pull) or use --force if they're sure.
Secret detection
If the script warns about potential secrets, tell the user which files were flagged and suggest reviewing them before using --force.
User Arguments
$ARGUMENTS
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 · 53 lines · 26 tokens per session scan B 4447ff010751
sync-push is a skill published in the GitHub repository rohithzr/claudebase (18 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 466 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…