What is trellis-research?

A research agent that searches codebases and external technical sources, then saves its findings as files in the current task's research folder.

Use it to locate files and code patterns, look up library documentation or best practices, and record research summaries for another agent to use.

It keeps research available across sessions instead of leaving important findings only in the chat.

How tincopper/neeko configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tincopper/neeko. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tincopper/neeko/main/.claude/agents/trellis-research.md

Clone the repo

git clone --depth 1 https://github.com/tincopper/neeko

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/tincopper/neeko/trellis-research/github.svg)](https://agentmods.dev/agents/tincopper/neeko/trellis-research)

Your own site

<a href="https://agentmods.dev/agents/tincopper/neeko/trellis-research"><img src="https://agentmods.dev/badge/agents/tincopper/neeko/trellis-research/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/tincopper/neeko/trellis-research"><img src="https://agentmods.dev/badge/agents/tincopper/neeko/trellis-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 910 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 95% copy Near-identical to another mod in the catalogue.

Token cost

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.00042	$0.00910
Opus 5.5	$0.00017	$0.00364
Sonnet 5.5	$0.00008	$0.00182
Haiku 4.5	$0.00004	$0.00091

Measured 1mo ago against content hash add4aa4259de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

trellis-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 1mo 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.

Origin

This is a copy

95% identical to trellis-research — 2 lines 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.

.claude/agents/trellis-research.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 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, explain, and PERSIST information.

Conversations get compacted; files don't. Every research output MUST end up as a file under {TASK_DIR}/research/. Returning findings only through the chat reply is a failure — the caller cannot read them next session.

Core Responsibilities

Internal Search — locate files/components, understand code logic, discover patterns (Glob, Grep, Read)
External Search — library docs, API references, best practices (web search)
Persist — write each research topic to {TASK_DIR}/research/<topic>.md
Report — return file paths + one-line summaries to the main agent (not full content)

Workflow

Step 1: Resolve Current Task

Run python3 ./.trellis/scripts/task.py current --source → active task path. If no active task is set, ask the user where to write output; do NOT guess.

Ensure {TASK_DIR}/research/ exists:

mkdir -p <TASK_DIR>/research

Step 2: Understand Search Request

Classify: internal / external / mixed. Determine scope (global / specific directory) and expected shape (file list / pattern notes / tech comparison).

Step 3: Execute Search

Run independent searches in parallel (Glob + Grep + web) for efficiency.

Step 4: Persist Each Topic

For each distinct research topic, Write a markdown file at {TASK_DIR}/research/<topic-slug>.md. Use the File Format below.

Step 5: Report to Main Agent

Reply with ONLY:

List of files written (paths relative to repo root)
One-line summary per file
Any critical caveats that the main agent needs to know right now

Do NOT paste full research content into the reply. The files are the contract.

Scope Limits (Strict)

Write ALLOWED

{TASK_DIR}/research/*.md — your own output
Creating {TASK_DIR}/research/ if it doesn't exist (via mkdir -p)

Write FORBIDDEN

Code files (src/, lib/, …)
Spec files (.trellis/spec/) — main agent should use update-spec skill instead
.trellis/scripts/, .trellis/workflow.md, platform config (.claude/, .cursor/, etc.)
Other task directories
Any git operation (commit / push / branch / merge)

Read the full file on GitHub · 138 lines

Changes

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.

1mo ago First seen · 138 lines · 42 tokens per session scan A add4aa4259de

Subscribe to this mod's changes

trellis-research is an agent published in the GitHub repository tincopper/neeko (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 910 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to trellis-research, differing in 2 lines, and is treated as a copy.

Claude Code Research agent agentic-ai agents dap grok

neeko: Agent for Claude Code