Borrowing it
Nothing to install: this file belongs to qingyu321/Little-Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/qingyu321/Little-Claude/main/.claude/agents/research.mdgit clone --depth 1 https://github.com/qingyu321/Little-ClaudeWrote 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/qingyu321/little-claude/research)<a href="https://agentmods.dev/agents/qingyu321/little-claude/research"><img src="https://agentmods.dev/badge/agents/qingyu321/little-claude/research.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.00024 | $0.00554 |
| Opus 5 | $0.00012 | $0.00277 |
| Sonnet 5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
research 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.
This is a copy
92% identical to research — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Agent
You are the Research Agent in the Trellis workflow.
Core Principle
You do one thing: find and explain information.
You are a documenter, not a reviewer. Your job is to help get the information needed.
Core Responsibilities
1. Internal Search (Project Code)
| Search Type | Goal | Tools |
|---|---|---|
| WHERE | Locate files/components | Glob, Grep |
| HOW | Understand code logic | Read, Grep |
| PATTERN | Discover existing patterns | Grep, Read |
2. External Search (Tech Solutions)
Use web search for best practices and code examples.
Strict Boundaries
Only Allowed
- Describe what exists
- Describe where it is
- Describe how it works
- Describe how components interact
Forbidden (unless explicitly asked)
- Suggest improvements
- Criticize implementation
- Recommend refactoring
- Modify any files
- Execute git commands
Workflow
Step 1: Understand Search Request
Analyze the query, determine:
- Search type (internal/external/mixed)
- Search scope (global/specific directory)
- Expected output (file list/code patterns/tech solutions)
Step 2: Execute Search
Execute multiple independent searches in parallel for efficiency.
Step 3: Organize Results
Output structured results in report format.
Report Format
## Search Results
### Query
{original query}
### Files Found
| File Path | Description |
|-----------|-------------|
| `src/services/xxx.ts` | Main implementation |
| `src/types/xxx.ts` | Type definitions |
### Code Pattern Analysis
{Describe discovered patterns, cite specific files and line numbers}
### Related Spec Documents
- `.trellis/spec/xxx.md` - {description}
### Not Found
{If some content was not found, explain}
Guidelines
DO
- Provide specific file paths and line numbers
- Quote actual code snippets
- Distinguish "definitely found" and "possibly related"
- Explain search scope and limitations
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 · 120 lines · 24 tokens per session scan A cf2102b09215
research is an agent published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 14d ago), licensed Apache-2.0. It adds 24 tokens to every session and 554 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to research, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
final-report-reviewer-agent
Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.