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 skills add billbuchanan-code/claude-code-power-setup --skill commitgit 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/commit)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/commit"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/commit"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/commit.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00624 |
| Opus 5.5 | $0.00014 | $0.00250 |
| Sonnet 5.5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
commit 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Skill
Stage, commit, and push the current changes following the user's established conventions.
When to Activate
Trigger this skill when the user says any of:
/commit- "push it"
- "commit this"
- "commit and push"
- "document, commit and push"
- "document commit and push"
Process
Step 1: Gather State (parallel)
Run these commands in parallel:
git status— see all modified, staged, and untracked filesgit diff --stat— summary of unstaged changesgit diff --cached --stat— summary of already-staged changesgit log --oneline -5— recent commit messages for style reference
Step 2: Determine What to Stage
- Stage all modified and new files that are part of the current work
- Never use
git add .orgit add -A— always stage specific files by name - Skip
.envfiles, credentials, secrets, and large binaries - If the user said "document" (e.g., "document, commit and push"), update relevant documentation before staging
Step 3: Write the Commit Message
- Read the recent git log output from Step 1 to match the repository's commit style
- Summarize the nature of changes: new feature, enhancement, bug fix, refactor, docs, etc.
- Use imperative mood ("Add feature" not "Added feature")
- Keep the first line under 72 characters
- Add a blank line and body if the changes warrant explanation
- End with:
Co-Authored-By: Claude <[email protected]> - Use a HEREDOC to pass the message to
git commit -m
Step 4: Commit and Push
Run sequentially:
git add <specific files>git commitwith the HEREDOC messagegit pushgit status— verify clean working tree
If the commit fails due to a pre-commit hook, fix the issue and create a new commit (never amend).
Step 5: Report
Output a brief summary:
- Files committed
- Commit message used
- Push status (success or any errors)
Rules
- Never amend a previous commit unless the user explicitly asks
- Never use
--no-verifyor skip hooks - Never force push unless explicitly asked (and warn if targeting main/master)
- If there are no changes to commit, say so and stop
- If pushing fails (e.g., no upstream), set upstream with
git push -u origin <branch>
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.
- 1mo ago First seen · 77 lines · 34 tokens per session scan A eb255c6dcb23
commit is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 624 once invoked, about $0.0001 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.