Borrowing it
Nothing to install: this file belongs to Sisyphe42/ReignsAgent. 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/Sisyphe42/ReignsAgent/master/.claude/agents/trellis-research.mdgit clone --depth 1 https://github.com/Sisyphe42/ReignsAgentWrote 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/sisyphe42/reignsagent/trellis-research)<a href="https://agentmods.dev/agents/sisyphe42/reignsagent/trellis-research"><img src="https://agentmods.dev/badge/agents/sisyphe42/reignsagent/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.1 | $0.00042 | $0.00909 |
| Opus 5 | $0.00021 | $0.00454 |
| 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 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
95% identical to trellis-research — 4 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 python ./.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.
- 8d ago First seen · 138 lines · 42 tokens per session scan A 10aecdd3d077
trellis-research is an agent published in the GitHub repository Sisyphe42/ReignsAgent (298 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 909 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 4 lines, and is treated as a copy.
Other agents, from other repositories
action-library-search
Search installed actions and read exemplar programs for learning (read-only).
readonly-explore
Read-only workspace exploration (Grep, Read, docs) — delegate broad file/code search.
startup-founder-studio
Use agents/00-startup-orchestrator/agent.md.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.