Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add e1024kb/wise-claude/plugin install wiseWrote 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/e1024kb/wise-claude/wise-commit)<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-commit"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-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/e1024kb/wise-claude/wise-commit"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-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.00179 | $0.01379 |
| Opus 5.5 | $0.00072 | $0.00552 |
| Sonnet 5.5 | $0.00036 | $0.00276 |
| Haiku 4.5 | $0.00018 | $0.00138 |
Grade A, and why
wise-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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wise-commit — draft a Conventional-Commits subject and commit
Preferred model: opus; preferred effort: low. Resolve availability before work;
do not silently substitute.
Before executing, follow model fallback for unavailable models or delegation routes, including in autonomous procedures.
At every skill start, identify your main/child role and the current client and GUI/TUI question tools, then read and follow the question lifecycle. Keep asynchronous prompts open until answered; this rule does not authorize questions in autonomous or otherwise prompt-free procedures.
Why this skill exists
/wise-commit-message is read-only on purpose: it drafts a subject
and hands it back, so the user can review, tweak, or reject the
prose before any commit object exists. That's the right shape when
the operator is sitting at the keyboard.
/wise-commit is the right shape when the operator already trusts
the drafter to pick the type, scope, and prose — they want one
call that stages tracked modifications, drafts the subject, and
commits. No clipboard round-trip, no second invocation.
The skill is a thin wrapper: read the shared
commit-routine.md, set PUSH=no
and SIMPLIFY=yes, and follow it. The routine is the source
of truth for staging discipline, the §2 pre-staging simplify
pass, ticket-reference detection, type classification, and the final-line
emit format. Pushing is /wise-commit-push's job; the per-caller
SIMPLIFY default policy lives in the routine's §"Inputs the
caller sets".
Invocation
/wise-commit
/wise:wise-commit # 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
If the user wants --no-verify, partial staging, or --amend, they
run git commit directly. This skill's argument surface is
deliberately empty so the routine's behaviour is predictable.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +5 lines 0734fc2d99cc
- 1mo ago Changed · +5 lines · -1 tokens per session 69c4934b42e6
- 1mo ago First seen · 137 lines · 180 tokens per session scan A cc20f2f12948
wise-commit is a skill published in the GitHub repository e1024kb/wise-claude (5 stars, last pushed 6d ago), licensed MIT. It adds 179 tokens to every session and 1,379 once invoked, about $0.0007 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
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
commit
Changelog and commit — lightweight motion for day-to-day plugin dev work in the monorepo. One commit per plugin scope; CHANGELOG and staging routed by detected slug. Trigger when the user says "commit", "commit this", "save this", "wrap this up", "let's commit", or finishes a change and wants to capture it. NOT for…
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.