Borrowing it
Nothing to install: this file belongs to OriginProtocol/origin-dollar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/OriginProtocol/origin-dollar/master/.claude/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/OriginProtocol/origin-dollarWrote 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/originprotocol/origin-dollar/commit)<a href="https://agentmods.dev/skills/originprotocol/origin-dollar/commit"><img src="https://agentmods.dev/badge/skills/originprotocol/origin-dollar/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/originprotocol/origin-dollar/commit"><img src="https://agentmods.dev/badge/skills/originprotocol/origin-dollar/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 53 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00062 | $0.01471 |
| Opus 5.5 | $0.00025 | $0.00588 |
| Sonnet 5.5 | $0.00012 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
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 12d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit It
Automates the full commit workflow: inspect changes, format code, stage files, generate a Conventional Commit message, and commit. Designed to be fast — the user said "commit it" because they want it done, not to answer a bunch of questions.
Instructions
1. Check Git State
First, make sure the repo is in a clean state for committing:
git status
If the repo is in the middle of a merge, rebase, or cherry-pick, inform the user and stop. These need to be resolved manually.
If there are no changes (nothing modified, nothing untracked), tell the user "Nothing to commit" and stop.
2. Inspect Changes
Run in parallel to understand what changed:
git diff(unstaged changes to tracked files)git diff --cached(already staged changes)git status --porcelain(all changes including untracked files — look for??lines)git log --oneline -5(recent commits for style reference)
Important: Untracked files (?? in git status) are often newly created files from the current session. They MUST be included in the commit alongside modified files.
3. Pre-Commit Formatting
Only run formatters relevant to the files that actually changed. Collect the full list of files to commit:
# Modified tracked files (staged + unstaged)
git diff --name-only
git diff --name-only --cached
# Untracked files (newly created)
git ls-files --others --exclude-standard
If any .sol files under contracts/tests/ changed:
forge fmt <those-files>
If any .sol files NOT under contracts/tests/ changed:
npx prettier --write --plugin=prettier-plugin-solidity <those-files>
If any files under src/js/ or JS config files changed:
yarn lint --fix
yarn prettier --write <changed-js-files>
Do NOT run formatters on the entire project — only pass the specific changed files.
If formatting fails and can't auto-fix, tell the user what's wrong and ask whether to proceed anyway.
4. Stage Files
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.
- 12d ago Changed · -1 lines d845c0cddc4f
- 1mo ago First seen · 175 lines · 62 tokens per session scan A 084baa5bbf25
commit is a skill published in the GitHub repository OriginProtocol/origin-dollar (153 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,471 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
git-workflow
Skill "git-workflow" from 0xlayerghost/solidity-agent-kit, covering git collaboration standards, language rule, commit rules, commit workflow and branch naming.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
trading-solana
Trade tokens on Solana DEXes - Jupiter, Raydium, Orca, Meteora, Pump.fun.
public
For agents: This document explains how to integrate with Clodds APIs.
pump-swarm
Coordinated multi-wallet trading on Pump.fun.