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.
npx agentmods add skills/galaxy-dawn/claude-scholar/git-workflownpx skills add Galaxy-Dawn/claude-scholar --skill git-workflowgit 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/skills/galaxy-dawn/claude-scholar/git-workflow)<a href="https://agentmods.dev/skills/galaxy-dawn/claude-scholar/git-workflow"><img src="https://agentmods.dev/badge/skills/galaxy-dawn/claude-scholar/git-workflow.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.1 | $0.00064 | $0.02851 |
| Opus 5 | $0.00032 | $0.01425 |
| Sonnet 5 | $0.00013 | $0.00570 |
| Haiku 4.5 | $0.00006 | $0.00285 |
Grade A, and why
git-workflow 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 6d 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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Standards
This document defines the project's Git usage standards, including commit message format, branch management strategy, workflows, merge strategies, and more. Following these standards improves collaboration efficiency, enables traceability, supports automation, and reduces conflicts.
Commit Message Standards
The project follows the Conventional Commits specification:
<type>(<scope>): <subject>
<body>
<footer>
Type Reference
| Type | Description | Example |
|---|---|---|
feat |
New feature | feat(user): add user export functionality |
fix |
Bug fix | fix(login): fix captcha not refreshing |
docs |
Documentation update | docs(api): update API documentation |
refactor |
Refactoring | refactor(utils): refactor utility functions |
perf |
Performance improvement | perf(list): optimize list performance |
test |
Test related | test(user): add unit tests |
chore |
Other changes | chore: update dependency versions |
Subject Rules
- Start with a verb: add, fix, update, remove, optimize
- No more than 50 characters
- No period at the end
For more detailed conventions and examples, see references/commit-conventions.md.
Branch Management Strategy
Branch Types
| Branch Type | Naming Convention | Description | Lifecycle |
|---|---|---|---|
| master | master |
Main branch, releasable state | Permanent |
| develop | develop |
Development branch, latest integrated code | Permanent |
| feature | feature/feature-name |
Feature branch | Delete after completion |
| bugfix | bugfix/issue-description |
Bug fix branch | Delete after fix |
| hotfix | hotfix/issue-description |
Emergency fix branch | Delete after fix |
| release | release/version-number |
Release branch | Delete after release |
Branch Naming Examples
feature/user-management # User management feature
feature/123-add-export # Issue-linked feature
bugfix/login-error # Login error fix
hotfix/security-vulnerability # Security vulnerability fix
release/v1.0.0 # Version release
What ships with it
9 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.
- examples/commit-messages.txt 1.0 KB
- examples/workflow-commands.sh 2.9 KB runs code
- references/advanced-usage.md 7.6 KB
- references/branching-strategies.md 4.0 KB
- references/collaboration.md 2.2 KB
- references/commit-conventions.md 3.3 KB
- references/conflict-resolution.md 2.6 KB
- references/gitignore-guide.md 4.2 KB
- references/merge-strategies.md 3.0 KB
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.
- 6d ago First seen · 478 lines · 64 tokens per session scan A bf38f307d02a
git-workflow is a skill published in the GitHub repository Galaxy-Dawn/claude-scholar (5,333 stars, last pushed 9d ago), licensed MIT. It adds 64 tokens to every session and 2,851 once invoked, about $0.0003 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 skills, from other repositories
research-brainstorm-from-kb
Explores and structures research ideas into obsidian-vault/ideas/ notes using the local paper knowledge base and frontier techniques. Use when the user provides research questions or ideas and wants decomposed candidate directions, related-work analysis based primarily on obsidian-vault/analysis, and cross-domain…
domain-fork
Migrates BITE's architecture to a new professional domain (e.g. frontend development, accounting, journalism). Interactive session with the user to map research concepts to domain equivalents, then generates a complete set of adapted skills and folder structure. Explicit trigger only.
papers-collect-from-github-repo
Collects paper candidates from any GitHub repository README or docs — awesome lists, survey companion repos, lab paper lists, conference accepted-paper repos, benchmark leaderboards, etc. Agent fetches the README (or specified doc), analyzes its format, writes a one-off parser, and outputs rows aligned with…
rf-obsidian-markdown
Obsidian Flavored Markdown conventions for BITE. Use when generating or editing any .md file in the vault (analysis notes, indexes, idea notes, wiki pages). Ensures all output is Obsidian-native and renders correctly in reading view, graph view, and backlink panels. Adapted from kepano/obsidian-skills (MIT).
code-context-paper-retrieval
Retrieves code-context-relevant papers from the local knowledge base in two modes (brief/deep), using obsidian-vault/analysis/ as the primary retrieval source and obsidian-vault/paperPDFs/ for optional deeper reading. obsidian-vault/index/ is optional and mainly serves statistics, Obsidian navigation, and backlink…
papers-download-from-list
Uses colocated paper download tools to download, verify, and repair local PDFs from obsidian-vault/paperlist.csv rows so that obsidian-vault/paperPDFs/ stays complete and deduplicated. Use when candidate rows are in state=Wait and should become Downloaded before the formal analysis chain.