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/billbuchanan-code/claude-code-power-setup/claude.sync.downnpx skills add billbuchanan-code/claude-code-power-setup --skill claude.sync.downgit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWhat 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.00016 | $0.00510 |
| Opus 5 | $0.00008 | $0.00255 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
claude.sync.down 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 2d 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
Claude Sync Down
Pull the latest changes from the private GitHub repo into the claude-dotfiles repo and sync them to ~/.claude/.
When to Activate
Trigger this skill when the user says:
/claude.sync.down- "pull dotfiles"
- "update dotfiles from github"
Process
Step 0: Detect Dotfiles Path
if [ -d ~/claude-dotfiles/.git ]; then echo ~/claude-dotfiles; elif [ -d ~/claude/claude-dotfiles/.git ]; then echo ~/claude/claude-dotfiles; else echo "NOT_FOUND"; fi
Store the result as DOTFILES_DIR. If NOT_FOUND, report the error and stop.
Step 1: Stash Local Changes
cd $DOTFILES_DIR && git status --short
If there are uncommitted local changes, stash them first:
cd $DOTFILES_DIR && git stash
Note whether a stash was created.
Step 2: Pull from Remote
cd $DOTFILES_DIR && git pull --rebase origin main
If pull shows "Already up to date." and no stash was created, report "Dotfiles already up to date." and stop.
Step 3: Pop Stash (if applicable)
If changes were stashed in Step 1:
cd $DOTFILES_DIR && git stash pop
If there are merge conflicts, report them to the user and stop — do not auto-resolve.
Step 4: Run Install Script
Re-run the install script to ensure symlinks and generated files are up to date:
cd $DOTFILES_DIR && bash install.sh
Step 5: Report
Output:
- Commits pulled (or "already up to date")
- Whether a stash was applied
- Any conflicts encountered
- Files synced to
~/.claude/
Rules
- Always
cd $DOTFILES_DIRbefore any git command - Never force-pull or reset — always rebase
- Never auto-resolve merge conflicts — report and stop
- Always sync to
~/.claude/after pulling
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.
- 2d ago First seen · 85 lines · 16 tokens per session scan A 244842aacadb
claude.sync.down is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 510 once invoked, about $0.0001 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-31.
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…