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.upnpx skills add billbuchanan-code/claude-code-power-setup --skill claude.sync.upgit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWrote 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/billbuchanan-code/claude-code-power-setup/claude.sync.up)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/claude.sync.up"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/claude.sync.up.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.00014 | $0.00487 |
| Opus 5 | $0.00007 | $0.00244 |
| Sonnet 5 | $0.00003 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
claude.sync.up 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 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.
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 Up
Commit any local changes in the claude-dotfiles repo and push them to the private GitHub repo.
When to Activate
Trigger this skill when the user says:
/claude.sync.up- "push dotfiles"
- "save dotfiles to 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: Check for Changes
cd $DOTFILES_DIR && git status --short
If there are no changes, report "Dotfiles already in sync — nothing to push." and stop.
Step 2: Gather Context (parallel)
cd $DOTFILES_DIR && git diff --stat— what changedcd $DOTFILES_DIR && git log --oneline -3— recent commit style
Step 3: Stage and Commit
- Stage specific changed files by name — never
git add .orgit add -A - Skip any files that look like secrets or credentials
- Write a conventional commit message summarizing the changes
- Use imperative mood, keep first line under 72 characters
- End with:
Co-Authored-By: Claude <[email protected]> - Use a HEREDOC for the message
Step 4: Push
cd $DOTFILES_DIR && git push
If push fails with no upstream, use git push -u origin main.
Step 5: Report
Output:
- Files committed
- Commit message
- Push status
Rules
- Always
cd $DOTFILES_DIRbefore any git command - Never amend previous commits
- Never use
--no-verifyor force push - Never commit secrets or
.envfiles
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 · 74 lines · 14 tokens per session scan A 86b69e12f53f
claude.sync.up is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 487 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
commit
Create structured git commits by analyzing staged and unstaged changes and grouping them logically into one or more commits with clear, descriptive messages. Use when the user asks to commit, says "commit this" or "commit my changes", wants help writing a commit message, or has finished a chunk of work that needs…