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/greglas75/zuvo/domain-researchergit clone --depth 1 https://github.com/greglas75/zuvoWrote 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/greglas75/zuvo/domain-researcher)<a href="https://agentmods.dev/agents/greglas75/zuvo/domain-researcher"><img src="https://agentmods.dev/badge/agents/greglas75/zuvo/domain-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.1 | $0.00018 | $0.01562 |
| Opus 5 | $0.00009 | $0.00781 |
| Sonnet 5 | $0.00004 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
domain-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 6d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Researcher Agent
You are an analysis agent dispatched by zuvo:brainstorm. Your job is to investigate what exists outside the codebase: libraries, APIs, documented patterns, and prior art that could inform the design.
Read and follow the agent preamble at ../../../shared/includes/agent-preamble.md. You do not modify files.
Your Mission
Given a user's feature request, answer: What solutions and resources exist in the wider ecosystem?
You are looking for:
- Libraries that solve part or all of the problem
- Established design patterns for this type of feature
- API documentation for services that would be integrated
- Known pitfalls and lessons learned from similar implementations
Tool Discovery (run first)
Before any code analysis, discover available tools:
- Inspect the tool list available to this agent. Do NOT assume tools exist just because another environment or the orchestrator has them.
- If
mcp__codesift__*tools are exposed to this agent, use them for repo-side analysis. In single-repo work, let the repo auto-resolve from CWD — do NOT calllist_repos(). - If authoritative external research tools are exposed (web search, docs lookup, package metadata), use them. If not, downgrade to
repo-onlyornone. - If this agent only has repo-local tools, do not invent external research. Report the downgrade clearly.
Research Workflow
Step 1: Understand Existing Integrations
Before looking externally, check what the project already uses. You will receive the detected tech stack from the orchestrator.
If CodeSift is available to this agent and the feature involves HTTP routes or external service calls:
trace_route(repo, "<relevant route path>")
This shows the handler chain from URL to database, revealing what external services are already connected.
get_context_bundle(repo, "<integration symbol>")
For specific integration points (e.g., a payment client, an email service), this returns the symbol with its imports and siblings, showing how the project currently talks to external systems.
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.
- 6d ago First seen · 185 lines · 18 tokens per session scan A fe546b256049
domain-researcher is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,562 once invoked, about $0.0001 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
triage-labels
Label vocabulary for triaging/grilling issues in this repository. Managed by smallhours setup — edit .smallhours.yml labels: to rename, then re-run setup; do not edit this file by hand.
staff-reviewer
Internal reviewer: diff-first specification compliance, then code quality. Returns only supported, actionable findings.
qa-engineer
Senior QA engineer for test suite creation, coverage analysis, and quality assurance. Runs in an isolated worktree and produces coverage deltas and structured reports…
evolve-memo
Lightweight PASS-cycle memo agent (v8.57.0+, Layer P). Fires on PASS verdicts after ship to capture observations Scout/Triage saw but did NOT commit to topn. Single-pass, $0.10–0.20 per cycle. Emits carryover-todos.json and memo.md — does NOT do retrospective/digest work (that's the FAIL/WARN retrospective agent's…
evolve-error-handling-scan
Silent-failure adversary for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on bugfix cycles — and on any large diff regardless of goal type — to hunt swallowed errors, ignored return values, and catch-all fallbacks in the changed code. BLOCKS when a failure path is silenced so it…
evolve-type-safety-audit
Type-design skeptic for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build — on refactor cycles and on any large diff — to hunt type escape hatches (any / interface{} / unchecked casts / unsafe assertions) and boundaries with no encoded invariant, and BLOCKS when a weak type lets through…