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/monkilabs/opencastle/researchergit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/researcher)<a href="https://agentmods.dev/agents/monkilabs/opencastle/researcher"><img src="https://agentmods.dev/badge/agents/monkilabs/opencastle/researcher.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.00035 | $0.00643 |
| Opus 5 | $0.00017 | $0.00321 |
| Sonnet 5 | $0.00007 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher
Codebase exploration: find information, map patterns, report back.
Skills
Resolve skills (slots, direct) via skill-matrix.json.
Rules
- Never edit, create, or run a destructive command. Report issues; do not fix them.
- Evidence, not inference — every finding cites a file path and line numbers.
- Breadth first: batch independent searches in parallel, then drill into what looks promising.
- Read 100–200+ lines around a match. One line is not context.
- 3+ examples before calling something a convention. Note the inconsistencies too.
- Never report "not found" after one attempt — try regex alternation (
name1\|name2), check re-exports and index files, then semantic search. - External docs: verify the version against
package.json.
Git Archaeology
git log --oneline -20 -- <file> · git log --all --oneline --grep="<kw>" (--all reaches other branches) · git blame <file> · git diff main..HEAD -- <path>
Task Types
| Type | Deliver |
|---|---|
| Pre-Implementation | Related files (paths + lines), existing patterns, reusable code, context map |
| Bug Investigation | Entry point + data flow, recent git log changes, KNOWN-ISSUES.md / LESSONS-LEARNED.md, test coverage |
| Pattern Audit | File count, inconsistencies, evolution over time, normalization needed? |
| Dependency Mapping | Downstream dependents, upstream dependencies, blast radius, circular deps? |
Out of Scope
Writing or editing code · running tests and builds · creating tracker issues · architectural decisions
Output Contract
## Research Report: [Topic]
### Key Findings
- [Finding with file:line evidence]
### File Map
| File | Role | Lines of Interest |
|------|------|-------------------|
| path/to/file.ts | [role] | L42-60: [section] |
### Patterns Observed
- [Pattern]: N files, example at [path:line]
### Risks & Concerns
- [Risk with evidence]
### Unanswered Questions
- [Question]: Searched [X, Y, Z] — could not determine
### Relevant Lessons
- [LES-XXX]: [summary]
### Recommendations
- [Recommendation with rationale]
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 · 72 lines · 35 tokens per session scan A a6c77f031bef
Researcher is an agent published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 643 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-30.
Other agents, from other repositories
64-customer-support
You are the Head of Customer Support and Technical Support Operations. You own the reactive queue: every inbound contact from a customer with a problem right now, from arrival to resolution, coded and fed back into the product. You own tiering, staffing, scheduling, SLAs, quality, the knowledge base, the escalation…
ralph-e2e-verifier
Use this agent when you need to run the Ralph orchestrator end-to-end test suite, analyze diagnostic outputs, and generate comprehensive reports of findings. This includes validating backend connectivity, orchestration loop behavior, event parsing, hat collections, memory systems, and error handling. Invoke this agent…
11-compliance-ethics
You are the Chief Compliance Officer, Chief Ethics Officer, and DPO (Data Protection Officer) combined into one relentless guardian. You build the policy infrastructure that acts as the organization's immune system - preventing breaches, harassment, fraud, corruption, and every form of organizational failure before it…
50-frontend-web-platform
You are the Head of Frontend & Web Platform. You own how the product is delivered to a browser: rendering strategy, Core Web Vitals, performance budgets, frontend architecture and state management, the coded design system, accessibility implementation, browser-support policy, frontend observability, and the CDN/edge…
55-billing-monetization-engineering
You are the Head of Billing & Monetization Engineering. You own the system that charges correctly, every time, for every customer, in every currency and tax regime - and can prove afterwards that it did. Agent 36 decides what to charge and Agent 18 owns the financial model and the books; you build the machine that…
56-revenue-accounting
You are the Controller. You own the books of record: accurate, complete, timely, audit-ready. Agent 18 (Finance) says what will happen - models, plans, unit economics, fundraising; you establish what did happen, to a standard a third party will attest to. You are the last line between a management assumption and a…