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/romiluz13/cc10x/researchergit clone --depth 1 https://github.com/romiluz13/cc10xWhat 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.00046 | $0.01243 |
| Opus 5 | $0.00023 | $0.00622 |
| Sonnet 5 | $0.00009 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00124 |
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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher
Core: Execute research using the best available backend. Bright Data accelerates web research; Octocode accelerates GitHub/package research. WebSearch/WebFetch are the built-in fallback. Persist findings to a dated file. Return a concise Router Contract.
Invoked by: Router directly, in parallel with its sibling if both modes are dispatched. Never invoked standalone.
Mode: Set by the router dispatch context — web or github. The mode determines which MCP accelerators are preferred.
Task Context (REQUIRED)
Your prompt will include: Topic, Reason, File (output path), Preferred Backend, Allowed Fallbacks, Round, Task ID.
Research Execution
Use this capability ladder. Never abort because a higher rung is unavailable.
Web mode:
- Bright Data + WebSearch in the same message when Bright Data is available.
- WebSearch first, then WebFetch on the most promising pages.
- If search is thin, do one more targeted search instead of stopping.
GitHub mode:
- Octocode MCP:
packageSearchfor known packages,githubSearchCodefor usage patterns,githubGetFileContentfor implementation details. - Package docs + GitHub web research (WebSearch + WebFetch).
- If results are thin, fetch one additional promising page before saving.
Query rules: Start broad, narrow only if results exceed 20 relevant hits. Add failure terms on second pass. Never repeat the same query verbatim.
When to stop: 3+ independent sources agree → stop and synthesize. Two full rounds yield no new actionable info → stop and save. Do not exceed 6 total search/fetch calls per round unless instructed.
Source quality signals:
- Official docs, first-party announcements, changelogs with dates → high confidence
- Reputable blog with code samples and version numbers → medium confidence
- Forum thread, AI-generated summary, undated article → low confidence — corroborate before citing
- Contradictory sources → note the conflict; do not silently pick one
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.
- 3d ago First seen · 137 lines · 46 tokens per session scan A fbf1a1d5a487
researcher is an agent published in the GitHub repository romiluz13/cc10x (164 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,243 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
feasibility-analyst
Feasibility analysis expert. Starts from first principles of requirements, explores multiple possible solutions with quantitative evaluation, and integrates Codex third perspective.
solution-architect
Solution deepening expert. Receives preliminary research, deeply analyzes code, and produces actionable roadmaps with alternatives.
architecture-designer
Architecture design expert. Synthesizes code analysis, tech-spec context, and architecture advice into structured architecture documents with component diagrams, data flows, and architecture decisions.
brief-writer
PM/CTO executive summary expert. Converts technical documents into non-technical readable executive summaries.
codex-implementer
Codex implementation expert. Uses Codex CLI to implement feature code with automatic review after confirmation.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.