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/e1024kb/wise-claude/wise-commit-pushnpx skills add e1024kb/wise-claude --skill wise-commit-pushgit clone --depth 1 https://github.com/e1024kb/wise-claudeWhat 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.00239 | $0.01879 |
| Opus 5 | $0.00120 | $0.00940 |
| Sonnet 5 | $0.00048 | $0.00376 |
| Haiku 4.5 | $0.00024 | $0.00188 |
Grade A, and why
wise-commit-push 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wise-commit-push — draft, commit, and push
Why this skill exists
/wise-commit closes the local loop — stage, draft, commit. The
common follow-up on a feature branch is git push. Bundling those
two steps into one call is the whole point of /wise-commit-push:
the operator types one command and the change lands on the remote.
The skill is a thin wrapper: read the shared
commit-routine.md (co-located
with /wise-commit, since that's the simpler skill that owns the
file), set PUSH=yes and SIMPLIFY=yes, and follow it. The
routine is the source of truth for the §2 pre-staging simplify
pass, staging, drafting, committing, the main/master push
refuse guard, the upstream check, and the final-line emit format.
The per-caller SIMPLIFY default policy lives in the routine's
§"Inputs the caller sets".
Invocation
/wise-commit-push
/wise:wise-commit-push # canonical namespaced form
No positionals, no flags. If the argument string contains anything other than optional whitespace, stop with:
Unknown argument(s): <the extra tokens>
Usage: /wise-commit-push
If the user wants --force, --no-verify, or any other escape
hatch, they run git push directly. This skill's argument surface
is deliberately empty so the routine's behaviour is predictable
and safe.
Procedure
1. Read the shared routine
Read ${CLAUDE_PLUGIN_ROOT}/skills/wise-commit/commit-routine.md
(the file ships alongside /wise-commit's SKILL.md).
2. Run the routine with PUSH=yes and SIMPLIFY=yes
Set PUSH=yes and SIMPLIFY=yes, then follow the routine
end-to-end. SIMPLIFY=yes runs the §2 simplify pass before
staging; PUSH=yes additionally enables §8 (push), which refuses
main / master / detached HEAD, refuses to auto-set a missing
upstream, and surfaces any git push error verbatim with no retry,
force, or --no-verify.
One subtle path stays worth knowing: if git add -A finds nothing to
stage but the local branch is ahead of upstream (a previous skill
already committed), the routine skips the draft/commit half and just
pushes the existing commits — the final COMMIT: ok subject="…"
reports the existing HEAD subject. Empty index AND nothing ahead →
COMMIT: skip reason="nothing to commit and nothing to push".
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 · 191 lines · 239 tokens per session scan A 1b5d7c0f0877
wise-commit-push is a skill published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed 7d ago), licensed MIT. It adds 239 tokens to every session and 1,879 once invoked, about $0.0012 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
commit
Commit message formatting and guidelines.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
keploy-pr-workflow
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.