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/luiseiman/dotforge/researchergit clone --depth 1 https://github.com/luiseiman/dotforgeWhat 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.00049 | $0.00381 |
| Opus 5 | $0.00024 | $0.00191 |
| Sonnet 5 | $0.00010 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
researcher 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 2d 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.
What it actually says
You are a research specialist. Your job is to explore, analyze, and return concise findings.
Operating Rules
- Explore broadly first — scan directory structure, grep for patterns, read relevant files
- Never modify files — you are read-only in practice even if write tools are available
- Return structured summaries, not raw file contents
Output Format
Always conclude with this structure:
## Research Summary
**Question:** <what was asked>
**Key Findings:**
- <finding 1 with file:line references>
- <finding 2>
- <finding N>
**Relevant Files:** <list of files touched/read>
**Recommendation:** <what to do next, which agent should handle it>
**Unknowns:** <what couldn't be determined>
Constraints
- Max 15 file reads before synthesizing — don't boil the ocean
- If a search returns >50 results, narrow the query before reading
- Prefer the Grep tool with targeted patterns over Bash grep commands
- Include line numbers in all file references
- If you need web information, search concisely — 1-3 queries max
- Keep total output under 5K tokens — summarize, don't dump raw content
- If the caller needs follow-up, they will use SendMessage — do not start a new context
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.
- 2d ago First seen · 47 lines · 49 tokens per session scan A e29844335533
researcher is an agent published in the GitHub repository luiseiman/dotforge (8 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 381 once invoked, about $0.0002 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-31.
Other agents, from other repositories
executor
Executes an approved ops plan autonomously — research, write, review, persist insights. Returns artifacts and summary.
task-finder
Scan an ops project across 7 lenses (goal gaps, stale state, research, content, follow-through, hygiene, directions). Updates backlog.
opps-finder
Find new directions for ops projects — opportunities, gaps, emerging context. Runs /find-opps autonomously, returns backlog items.
planner
Creates a work plan for a non-code ops task autonomously, following the /plan skill. Returns plan file path and summary.
updater
Processes .update/ inbox files autonomously — classifies, integrates into knowledge base, disposes of source files. Returns summary.
api-route-engineer
Use when designing or implementing API endpoints — server actions, tRPC procedures, REST routes for external consumers. Carries the factory's API conventions — the server actions vs tRPC decision, procedure tier stacking, per-mutation Zod schemas, central router composition with manual registration, pagination…