Claude Scholar is a semi-automated research assistant for academic research and software development, supporting literature review, coding, experiments, reporting, writing, and project knowledge management. Computer science and AI researchers use it across the research workflow with several coding-agent platforms; the catalogue contains its skills, commands, agents, hooks, plugin, and instruction.
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.
git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholarWrote 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/commands/galaxy-dawn/claude-scholar/update-github)<a href="https://agentmods.dev/commands/galaxy-dawn/claude-scholar/update-github"><img src="https://agentmods.dev/badge/commands/galaxy-dawn/claude-scholar/update-github/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/commands/galaxy-dawn/claude-scholar/update-github"><img src="https://agentmods.dev/badge/commands/galaxy-dawn/claude-scholar/update-github.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.00015 | $0.00590 |
| Opus 5.5 | $0.00006 | $0.00236 |
| Sonnet 5.5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
update-github 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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update GitHub
Commit uncommitted changes and push to remote GitHub repository.
Instructions
-
Check Git Status
- Run
git status - Show all uncommitted changes
- Run
-
Analyze Changes
- Review changed files
- Determine commit type (feat/fix/docs/refactor/test/chore)
- Determine scope (affected module/component)
-
Create Commit Message Follow Conventional Commits format:
<type>(<scope>): <subject> <body> <footer>Types:
feat: 新功能fix: Bug 修复docs: 文档更新refactor: 代码重构perf: 性能优化test: 测试相关chore: 其他修改
-
Stage and Commit
- Run
git addfor affected files - Create commit with formatted message
- Do not include
Co-Authored-Byfooters unless the user explicitly asks for them
- Run
-
Push to Remote
- Run
git push - If rejected, pull with rebase first:
git pull --rebase origin $(git branch --show-current) git push
- Run
-
Verify Success
- Show commit SHA
- Show remote branch status
Example Usage
User: /update-github
1. Checking git status...
Modified: src/utils/helpers.py
Modified: README.md
2. Analyzing changes...
- src/utils/helpers.py: Refactored helper functions
- README.md: Updated documentation
3. Proposed commit:
docs(readme): 更新项目文档
- 添加使用示例
- 更新依赖说明
4. Proceed? (yes/no/modify)
5. Staging files...
git add src/utils/helpers.py README.md
6. Creating commit...
[main abc1234] docs(readme): 更新项目文档
7. Pushing to remote...
git push
To github.com:user/repo.git
abc1234..def5678 main -> main
✅ Successfully pushed to GitHub!
Arguments
$ARGUMENTS can be:
--amend- Amend last commit instead of creating new one--no-verify- Skip pre-commit hooks<type>(<scope>): <message>- Use custom commit message
Integration
This command uses the same Conventional Commits format as the /commit skill but focuses on the complete flow: stage → commit → 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.
- 1mo ago First seen · 101 lines · 15 tokens per session scan A 4b68f687041d
update-github is a command published in the GitHub repository Galaxy-Dawn/claude-scholar (5,867 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 590 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-30.
Other commands, from other repositories
pre-commit-audit
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers. Use when the user requests a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode…
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.