Borrowing it
Nothing to install: this file belongs to bitbankinc/bitbank-mcp-server. 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/bitbankinc/bitbank-mcp-server/main/.cursor/skills/lint-and-commit/SKILL.mdgit clone --depth 1 https://github.com/bitbankinc/bitbank-mcp-serverWrote 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/bitbankinc/bitbank-mcp-server/lint-and-commit)<a href="https://agentmods.dev/skills/bitbankinc/bitbank-mcp-server/lint-and-commit"><img src="https://agentmods.dev/badge/skills/bitbankinc/bitbank-mcp-server/lint-and-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/bitbankinc/bitbank-mcp-server/lint-and-commit"><img src="https://agentmods.dev/badge/skills/bitbankinc/bitbank-mcp-server/lint-and-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.00071 | $0.00571 |
| Opus 5 | $0.00036 | $0.00285 |
| Sonnet 5 | $0.00014 | $0.00114 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
lint-and-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 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.
What it actually says
lint-and-commit
lint/format を実行し、未コミットの差分からコミットメッセージを生成してコミットする。
手順
Step 1: lint/format を実行
npm run format:fix
lint エラーがある場合は修正してから次へ進む。
Step 2: 未コミットの差分を確認
git diff
git diff --cached # staged の変更も確認
git diff --stat
Step 3: コミットメッセージを作成
差分の内容から Conventional Commits 形式のコミットメッセージを提案する。
形式:
<type>(<scope>): <subject>
scope は省略可能（例: feat: add validation でも feat(trade): add validation でも可）。
type の選択:
| type | 用途 |
|---|---|
feat |
機能追加 |
fix |
バグ修正 |
docs |
ドキュメント変更 |
refactor |
リファクタリング |
style |
フォーマット変更 |
test |
テストの追加・修正 |
chore |
ビルド・設定変更 |
ルール:
- 英語で記述する
- subject は 50 文字以内目安
例:
feat(get-ticker): add sell/buy spread calculation
fix(get-candles): correct datetime format conversion
chore: update biome config
test(get-depth): add unit tests for depth formatting
docs: update README with new tool description
Step 4: ユーザーに確認してコミット
提案したコミットメッセージをユーザーに伝え、確認を得てから実行する:
git add -A # または個別に git add <ファイル>
git commit -m "<コミットメッセージ>"
注意
- コミットは必ずユーザーの確認後に実行する
- push はユーザーが行う想定のため実行しない
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 First seen · 77 lines · 71 tokens per session scan A 8232c38d1ced
lint-and-commit is a skill published in the GitHub repository bitbankinc/bitbank-mcp-server (0 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 571 once invoked, about $0.0004 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. 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.
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…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…