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-pullnpx skills add rohithzr/claudebase --skill sync-pullgit clone --depth 1 https://github.com/rohithzr/claudebaseWhat 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.00027 | $0.00467 |
| Opus 5 | $0.00014 | $0.00234 |
| Sonnet 5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade B, and why
sync-pull 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `--include-global` — Also pull `~/.claude/settings.json` (global settings are opt-in) What it actually says
Config Sync Pull
Pull configuration from your GitHub backup repo and apply it to the local machine.
What happens
- Backup — Current local config is backed up to plugin data directory (timestamped, keeps last 10)
- Apply shared — Files from
shared/directory are applied first (base layer) - Apply profile — Profile-specific files overlay on top (overrides shared where both exist)
- Apply global — User-level settings from
global/are applied to~/.claude/ - Verify — JSON config files are validated for correct syntax
Instructions
Parse user arguments and run the pull script:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync-pull.sh" [OPTIONS]
Options:
--profile NAME— Pull a specific profile (default: active profile)--dry-run— Show what would be applied without writing any files--no-backup— Skip backup step (use with caution)--yes/-y— Skip confirmation prompt (auto-approve)--include-global— Also pull~/.claude/settings.json(global settings are opt-in)
Profile switching
If the user specifies a different profile than their current one, this effectively switches their setup. Let them know which profile they're switching from/to.
After pull
Tell the user:
- How many files were applied
- Any validation warnings
- That a backup was created (and where)
- They may need to restart Claude Code for some settings to take effect
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 · 54 lines · 27 tokens per session scan B 633f419cf4a1
sync-pull is a skill published in the GitHub repository rohithzr/claudebase (18 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 467 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…