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-setupnpx skills add rohithzr/claudebase --skill sync-setupgit 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-setup)<a href="https://agentmods.dev/skills/rohithzr/claudebase/sync-setup"><img src="https://agentmods.dev/badge/skills/rohithzr/claudebase/sync-setup.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.00032 | $0.00429 |
| Opus 5 | $0.00016 | $0.00215 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade B, and why
sync-setup 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Linux**: `sudo apt install gh` or `sudo dnf install gh` What it actually says
Config Sync Setup
Initialize Claude Config Sync by connecting to GitHub and creating the backup repository.
What this does
- Verifies
ghCLI is installed and authenticated - Creates a private GitHub repo for config storage (or connects to existing)
- Initializes the repo structure with a default profile
- Performs the first push of your current Claude Code config
Instructions
Run the setup script. Parse user arguments for custom repo name and profile:
- First argument (if provided): repo name (default:
claude-config) - Second argument (if provided): initial profile name (default:
default)
bash "${CLAUDE_PLUGIN_ROOT}/scripts/ensure-repo.sh" REPO_NAME PROFILE_NAME
Replace REPO_NAME and PROFILE_NAME with the user's values or defaults.
If gh is not installed
Guide the user to install it:
- macOS:
brew install gh - Linux:
sudo apt install ghorsudo dnf install gh - Windows:
winget install --id GitHub.cli
Then authenticate: gh auth login
After setup succeeds
Run the first push automatically:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync-push.sh" --profile PROFILE_NAME
Tell the user what was synced and show all available commands: /sync-push, /sync-pull, /sync-status, /sync-profiles, /sync-config.
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.
- 3d ago First seen · 58 lines · 32 tokens per session scan B b5dc0ca0273a
sync-setup is a skill published in the GitHub repository rohithzr/claudebase (18 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 429 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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…