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 commands/galaxy-dawn/claude-scholar/commitgit clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholarWhat 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.00014 | $0.00378 |
| Opus 5 | $0.00007 | $0.00189 |
| Sonnet 5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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 2d 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
Commit
Stage and commit changes using Conventional Commits format.
Instructions
-
Check Git Status
- Run
git statusto review all changes - Run
git diffto inspect modifications
- Run
-
Analyze Changes
- Review changed files and their content
- Determine commit type and scope
- Draft a concise commit message
-
Commit Type Reference
feat - New feature fix - Bug fix docs - Documentation only style - Code style (formatting, semicolons, etc.) refactor - Code refactoring (no feature/fix) perf - Performance improvement test - Adding or updating tests chore - Build, CI, tooling, dependencies -
Commit Message Format
<type>(<scope>): <subject> <body>- Subject: imperative mood, no period, max 72 chars
- Body: explain what and why (optional for small changes)
- Scope: affected module (data, model, config, trainer, utils, workflow)
-
Stage and Commit
- Stage relevant files with
git add - Do NOT stage files containing secrets (.env, credentials, tokens)
- Create commit with formatted message
- Do not include
Co-Authored-Byfooters unless the user explicitly asks for them - Verify with
git log --oneline -1
- Stage relevant files with
Notes
- This command only commits locally. Use
/update-githubto also push. - Always confirm the commit message with the user before committing.
- If unsure about type or scope, ask the user.
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.
- 2d ago First seen · 54 lines · 14 tokens per session scan A 013723ee3789
commit is a command published in the GitHub repository Galaxy-Dawn/claude-scholar (5,297 stars, last pushed 6d ago), licensed MIT. It adds 14 tokens to every session and 378 once invoked, about $0.0001 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-30.
Other commands, from other repositories
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
commit-all
Group all changes semantically and commit each group separately.
commit
Based on the above changes, create a single git commit.
commit
Safe git commit practices for MindRoom.
brief
Command "brief" from csmar432/finai-research, covering brief — 生成研究简报, arguments, 描述, 工作方式 and 示例.
commit
智能生成 Git 提交信息并提交.