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/matheuspavaneli/workbench/write-commitnpx skills add matheusPavaneli/workbench --skill write-commitgit clone --depth 1 https://github.com/matheusPavaneli/workbenchWhat 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.00042 | $0.00627 |
| Opus 5 | $0.00021 | $0.00313 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
write-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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
write-commit
python "${CLAUDE_PLUGIN_ROOT}/lib/wb.py" <args>
This skill writes the message. Committing stays the user's call: the CLI prints
the command and runs it only for an explicit --execute.
Steps
-
Learn the house style.
commit convention. It reports what this repo already does — conventional commits, ticket-prefixed subjects, or free-form — from its own history, plus the author identity and whether it matches the context. Follow it; a message in a different style is noise in the log forever. If it reportsfree-formand the team has decided to adopt a style, record it once withcommit convention --set <style>— do not impose one silently. -
See what changed.
git difffor the files,review contextif you need the zones. If a plan exists:sdd get <KEY> --section summarygives the objective in one line. -
Write it.
- Subject: imperative, specific, under 72 characters, no trailing period. "fix expired coupon charging the card" — not "fixes" and not "bug fix".
- Body, when the change is not self-evident: why, not what. The diff already says what. Wrap at 72.
- Reference the ticket key if the repo's history does.
BREAKING CHANGE:in the body if a contract changed.
-
Check it. Write the draft to a file, then
commit check --file <path> --key <KEY>. On pass with a key it is saved to.workflow/<KEY>/commit.txt; on failure nothing is saved and the reasons are listed. Fix the message, not the check. -
Hand it over. Show the message.
git commit <KEY>prints the exact commit command, carrying the saved message and the author the context expects; add--executeonly if the user asked you to commit. It refuses on a protected branch and with nothing staged — choosing what goes in a commit stays theirs.
Rules
- One logical change per commit. If the subject needs an "and", it is probably two commits.
- Never describe what you did not do. No "add tests" in the subject when no test file changed.
- No unfinished markers.
wip,fixup!andsquash!are rejected. - Never put a credential in a message. The check refuses anything that looks like one.
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.
- yesterday First seen · 57 lines · 42 tokens per session scan A eb173e927511
write-commit is a skill published in the GitHub repository matheusPavaneli/workbench (1 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 627 once invoked, about $0.0002 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
integration-rule-engine
A declarative routing engine that turns ticket / error attributes (reporter, label, project, area path, error class, environment) into a tag + AI agent + priority assignment, so cross-source workflows ("security tickets always go to the OWASP reviewer") stay out of code and in user-editable rules.
stale-ticket-triage
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
apple-container
Apple's open-source container CLI to build, run, and manage OCI/Linux containers as lightweight per-container VMs on Apple-silicon macOS — no Docker daemon required. Use when the user mentions the container CLI, "apple container", running or building containers on macOS without Docker/Podman, container run, container…
atlassian
Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via…
google-calendar
Interact with Google Calendar - list calendars, view events, create/update/delete events, and find free time. Use when user asks to: check calendar, schedule a meeting, create an event, find available time, list upcoming events, delete or update a calendar event, or respond to meeting invitations. Lightweight…