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 skills add Galaxy-Dawn/claude-scholar --skill skill-developmentgit 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/skill-development)<a href="https://agentmods.dev/skills/galaxy-dawn/claude-scholar/skill-development"><img src="https://agentmods.dev/badge/skills/galaxy-dawn/claude-scholar/skill-development/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/galaxy-dawn/claude-scholar/skill-development"><img src="https://agentmods.dev/badge/skills/galaxy-dawn/claude-scholar/skill-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00961 |
| Opus 5 | $0.00022 | $0.00481 |
| Sonnet 5 | $0.00009 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
skill-development 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 5d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Development
Use this skill to create or repair Claude skills in the current local environment, not in an abstract plugin template.
Goal
Produce a skill that is:
- easy to trigger,
- lean at the
SKILL.mdlayer, - backed by real
references/,examples/, andscripts/files when they are mentioned, - free of dead local references.
Core rules
- Keep one skill = one durable job.
- Treat the frontmatter description as the main trigger surface.
- Keep
SKILL.mdfocused on workflow and boundaries. - Move detailed catalogs, templates, and long explanations into
references/orexamples/. - Do not mention files that do not exist.
- Do not inherit stale names, agents, or sibling skill references without verifying they exist locally.
Default workflow
1. Inspect the current environment first
Before writing anything:
- inspect the target skill directory,
- inspect neighboring skills that already solve a similar problem,
- verify which agents, commands, and sibling skills actually exist,
- identify stale references before adding new ones.
Use the local inventory as the authority. Do not write guidance against an imagined plugin layout.
2. Lock the skill contract
Define four things before editing:
- what the skill does,
- what triggers it,
- what it explicitly does not do,
- which bundled resources are actually needed.
If the skill only needs a short workflow, keep it short. Do not create references/, examples/, or scripts/ just because the directories are conventional.
3. Write or repair the frontmatter
The frontmatter should:
- use the real skill identifier in
name, - use a third-person trigger description,
- include concrete phrases a user would naturally say,
- stay short enough to scan quickly.
Prefer descriptions of this form:
---
name: skill-name
description: This skill should be used when the user asks to "...", "...", or needs help with ....
---
4. Keep the main file lean
A good SKILL.md should usually contain:
- a short goal section,
- role boundaries,
- a default workflow,
- safety or quality rules,
- a short list of additional resources.
What ships with it
3 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.
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.
- 5d ago First seen · 133 lines · 43 tokens per session scan A e26c63898c9e
skill-development is a skill published in the GitHub repository Galaxy-Dawn/claude-scholar (5,381 stars, last pushed 12d ago), licensed MIT. It adds 43 tokens to every session and 961 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.
research
Performs deep research on a topic via deepresearch. Simulates a multi-step research process and returns a comprehensive research result as a string.
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
do-it-core
Use when repository work needs a shared baseline for intent, facts, causal changes, and honest evidence.
do-it-context
Use when project terms, relationships, or invariants drift between user language, docs, and implementation.
do-it-handbook
Use when repeated rediscovery of stable project knowledge makes a small shared handbook useful.