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 agentmods add agents/tincopper/neeko/trellis-researchgit clone --depth 1 https://github.com/tincopper/neekoWrote 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/tincopper/neeko/trellis-research)<a href="https://agentmods.dev/agents/tincopper/neeko/trellis-research"><img src="https://agentmods.dev/badge/agents/tincopper/neeko/trellis-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 | $0.00042 | $0.00910 |
| Opus 5 | $0.00021 | $0.00455 |
| Sonnet 5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
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 4d 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
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.
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 (viamkdir -p)
Write FORBIDDEN
- Code files (
src/,lib/, …) - Spec files (
.trellis/spec/) — main agent should useupdate-specskill instead .trellis/scripts/,.trellis/workflow.md, platform config (.claude/,.cursor/, etc.)- Other task directories
- Any git operation (commit / push / branch / merge)
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.
- 4d ago First seen · 138 lines · 42 tokens per session scan A add4aa4259de
trellis-research is an agent published in the GitHub repository tincopper/neeko (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 910 once invoked, about $0.0002 per session on Opus 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.
Other agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
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.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…