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/tdd)<a href="https://agentmods.dev/commands/galaxy-dawn/claude-scholar/tdd"><img src="https://agentmods.dev/badge/commands/galaxy-dawn/claude-scholar/tdd/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/tdd"><img src="https://agentmods.dev/badge/commands/galaxy-dawn/claude-scholar/tdd.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.00028 | $0.02185 |
| Opus 5 | $0.00014 | $0.01092 |
| Sonnet 5 | $0.00006 | $0.00437 |
| Haiku 4.5 | $0.00003 | $0.00218 |
Grade A, and why
tdd 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 9d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Command
This command enforces a test-driven development methodology directly.
What This Command Does
- Scaffold Interfaces - Define types/interfaces first
- Generate Tests First - Write failing tests (RED)
- Implement Minimal Code - Write just enough to pass (GREEN)
- Refactor - Improve code while keeping tests green (REFACTOR)
- Verify Coverage - Ensure 80%+ test coverage
When to Use
Use /tdd when:
- Implementing new features
- Adding new functions/components
- Fixing bugs (write test that reproduces bug first)
- Refactoring existing code
- Building critical business logic
How It Works
This command should:
- Define interfaces for inputs/outputs
- Write tests that will FAIL (because code doesn't exist yet)
- Run tests and verify they fail for the right reason
- Write minimal implementation to make tests pass
- Run tests and verify they pass
- Refactor code while keeping tests green
- Check coverage and add more tests if below 80%
TDD Cycle
RED → GREEN → REFACTOR → REPEAT
RED: Write a failing test
GREEN: Write minimal code to pass
REFACTOR: Improve code, keep tests passing
REPEAT: Next feature/scenario
Example Usage
User: /tdd I need a function to calculate market liquidity score
Assistant:
# TDD Session: Market Liquidity Score Calculator
## Step 1: Define Interface (SCAFFOLD)
```python
# lib/liquidity.py
from dataclasses import dataclass
from datetime import datetime
from typing import NotRequired
@dataclass
class MarketData:
totalVolume: float
bidAskSpread: float
activeTraders: int
lastTradeTime: datetime
def calculateLiquidityScore(market: MarketData) -> float:
# TODO: Implementation
raise NotImplementedError('Not implemented')
Step 2: Write Failing Test (RED)
# tests/test_liquidity.py
import pytest
from lib.liquidity import calculateLiquidityScore, MarketData
from datetime import datetime
def test_liquid_market_high_score():
"""Test that liquid market gets high score."""
market = MarketData(
totalVolume=100000,
bidAskSpread=0.01,
activeTraders=500,
lastTradeTime=datetime.now()
)
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.
- 9d ago First seen · 325 lines · 28 tokens per session scan A 90a49a5f129c
tdd is a command published in the GitHub repository Galaxy-Dawn/claude-scholar (5,381 stars, last pushed 12d ago), licensed MIT. It adds 28 tokens to every session and 2,185 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
pair
AI pair programming — switch between Driver, Navigator, TDD, Review, and Debug modes.
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
tdd
A command for test-driven development, a method where you write a failing test first, then code to pass it, and finally improve the code.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first.
feature-implement-execute
Phase 4 of develop: Execute the implementation plan with per-task TDD, quality gates, and completion verification.