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/noahlz/claude-plugins/commit-with-costsnpx skills add noahlz/claude-plugins --skill commit-with-costsgit clone --depth 1 https://github.com/noahlz/claude-pluginsWrote 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.svg" alt="Measured on agentmods" 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 | $0.00031 | $0.01216 |
| Opus 5 | $0.00015 | $0.00608 |
| Sonnet 5 | $0.00006 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade B, and why
commit-with-costs scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/settings.plugins.commit-with-costs.json How it starts
The opening of the file, as written. The whole thing — 149 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").
SKILL_BASE_DIR: ${CLAUDE_SKILL_DIR}
If the above shows literal ${CLAUDE_SKILL_DIR}, halt: "Requires Claude Code 2.1.69+."
Node.js Check: !node "${CLAUDE_SKILL_DIR}/../../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_SKILL_DIR}/../../lib/check-dependencies.js" "${CLAUDE_SKILL_DIR}/../.."
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_SKILL_DIR}/../../lib/check-skill-config.js" "./.claude/settings.plugins.commit-with-costs.json"
✓ Configuration found→ Step 1aNOT_CONFIGURED→ Step 1b
1. Resolve SessionID
1a. Load existing configuration
cat .claude/settings.plugins.commit-with-costs.json
Extract sessionId → SESSION_ID. Proceed to Step 2.
1b. Create new configuration
Display: "Configuration not found (./.claude/settings.plugins.commit-with-costs.json). Let's create it."
node "{{SKILL_BASE_DIR}}/scripts/commit-workflow.js" list-sessions
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.
- 4d 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 2d ago), licensed MIT. It adds 31 tokens to every session and 1,216 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…