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 noahlz/claude-plugins/plugin install dev-workflowWrote 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/noahlz/claude-plugins/commit-with-costs)<a href="https://agentmods.dev/skills/noahlz/claude-plugins/commit-with-costs"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/commit-with-costs/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/noahlz/claude-plugins/commit-with-costs"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/commit-with-costs.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.00031 | $0.01243 |
| Opus 5.5 | $0.00012 | $0.00497 |
| Sonnet 5.5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
commit-with-costs 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 8d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a git commit with cost metric trailers and Claude attribution.
Activate only when user invokes /commit-with-costs or asks to commit with costs (e.g. "commit with costs", "commit and track costs").
PLUGIN_ROOT: ${CLAUDE_PLUGIN_ROOT}
Node.js Check: !node "${CLAUDE_PLUGIN_ROOT}/lib/check-node-version.js"
Halt if ERROR.
Git Instructions Check: !node "${CLAUDE_SKILL_DIR}/scripts/check-git-instructions.js"
Display any WARNING before proceeding.
Dependencies: !node "${CLAUDE_PLUGIN_ROOT}/lib/check-dependencies.js" "${CLAUDE_PLUGIN_ROOT}"
Rules
| Rule | Behavior |
|---|---|
| DELEGATE_TO | Read the referenced file; execute its instructions exactly. Never improvise or guess commands. |
| Narration | Narrate only STEP_DESCRIPTION steps; all others silent. |
| JSON outputs | Extract fields into variables (e.g. data.session_id → SESSION_ID). |
| Cost metrics | Never fabricate or estimate. Only use values from successful ccusage execution. |
Checklist
- [ ] 0. Pre-flight and config
- [ ] 1. Resolve SessionID
- [ ] 2. Detect or Generate Commit Message
- [ ] 3. Get User Approval
- [ ] 4. Fetch Cost Data
- [ ] 5. Create commit
- [ ] 6. Display Final Summary
0. Pre-flight and Config
Halt if git commands already ran in this turn.
SKILL_CONFIG: !node "${CLAUDE_PLUGIN_ROOT}/lib/skill-config.js" check commit-with-costs
- Starts with
✓ Configuration found→ Step 1a - Starts with
NOT_CONFIGURED→ Step 1b
Config lives at the project root. Access it only via skill-config.js, never by relative path.
1. Resolve SessionID
1a. Load existing configuration
node "${CLAUDE_PLUGIN_ROOT}/lib/skill-config.js" read commit-with-costs
Extract config.sessionId → SESSION_ID. Proceed to Step 2.
1b. Create new configuration
Display: "Configuration not found ({{path from SKILL_CONFIG}}). Let's create it."
node "${CLAUDE_SKILL_DIR}/scripts/commit-workflow.js" list-sessions
Extract data.sessions. Use AskUserQuestion: "Select a Claude Code session:" with first 4 session IDs as options.
What ships with it
5 files 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.
- 8d ago Changed · +1 lines scan B → A cdab54b4d225
- 1mo ago First seen · 149 lines · 31 tokens per session scan B 85fed2146b88
commit-with-costs is a skill published in the GitHub repository noahlz/claude-plugins (5 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 1,243 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…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.