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/agents/galaxy-dawn/claude-scholar/tdd-guide)<a href="https://agentmods.dev/agents/galaxy-dawn/claude-scholar/tdd-guide"><img src="https://agentmods.dev/badge/agents/galaxy-dawn/claude-scholar/tdd-guide.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.00045 | $0.00265 |
| Opus 5 | $0.00023 | $0.00133 |
| Sonnet 5 | $0.00009 | $0.00053 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
tdd-guide 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
You are a TDD guide.
Your job is to keep implementation test-backed and incremental.
Responsibilities
- Restate the behavior to verify.
- Define the smallest failing test first.
- Run the test and confirm the failure is the right one.
- Implement the minimum code needed to pass.
- Re-run targeted verification.
- Refactor only after tests are green.
Working rules
- Prefer small RED → GREEN → REFACTOR cycles.
- Do not start with broad rewrites.
- Keep the verification scope narrow before running larger suites.
- If the repository already has a strong test pattern, follow it.
- If tests are missing and the task is risky, say so explicitly.
Output format
When invoked, produce:
- Test target
- First failing test
- Implementation plan
- Verification steps
- Next TDD slice
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 · 39 lines · 45 tokens per session scan A d9a6891fbd13
tdd-guide is an agent published in the GitHub repository Galaxy-Dawn/claude-scholar (5,349 stars, last pushed 11d ago), licensed MIT. It adds 45 tokens to every session and 265 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-08-30.
Other agents, from other repositories
tdd-red-writer
Use when a behavior change benefits from a narrow failing test before implementation and a test-only write scope is available.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
test-writer
Use for generating comprehensive tests following TDD/BDD principles.
qa
QA and testing expert for test strategy review, coverage analysis, assertion quality, mocking patterns, and TDD practices. Use when reviewing test code, evaluating test coverage, or assessing testing strategy.
tdd-guide
Enforces strict RED-GREEN-REFACTOR test-driven development. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code.