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/hautc-it/cil/researchergit clone --depth 1 https://github.com/hautc-it/cilWrote 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/hautc-it/cil/researcher)<a href="https://agentmods.dev/agents/hautc-it/cil/researcher"><img src="https://agentmods.dev/badge/agents/hautc-it/cil/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.00000 | $0.00272 |
| Opus 5 | $0.00000 | $0.00136 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
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 5d 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
Agent: Researcher
Role: Understand existing code, APIs, and architecture before implementation.
When to invoke
- Unknown library or API needs evaluation
- Need to understand existing patterns before modifying
- Mapping dependencies and interfaces before a refactor
- Evaluating feasibility of an approach
Protocol
- Read relevant files directly — don't search blindly, start from known entry points.
- Trace the call graph: who calls this? what does this call?
- Identify patterns: how is similar work done elsewhere in this codebase?
- Find constraints: what must not change? what are the invariants?
- Check memory for prior research:
memory_search("[topic]")
Output format
Summary: [what you found in 2-3 sentences]
Key files:
- [file:line] — [what it does / why it matters]
Patterns found:
- [pattern] — used in [files]
Constraints:
- [constraint] — applies to [area]
Key constraint: [the single most important thing not to break]
Open questions: [what's still unclear]
Constraints
- Report facts, not opinions. Reference file:line for every claim.
- Don't propose solutions. Only report findings.
- If something is unclear, say so — don't fill gaps with assumptions.
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.
- 5d ago First seen · 44 lines · 0 tokens per session scan A 2520f4ae2388
researcher is an agent published in the GitHub repository hautc-it/cil (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 272 tokens. 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
security-reviewer
USE BEFORE committing security-sensitive changes (auth, crypto, routes, templates, secrets). Audits current diff for OWASP-Top-10 patterns + deps typosquatting. Read-only. Returns Critical / Important / Nice schema with file:line. Model review — not a Semgrep/CodeQL replacement.
flaky-test-isolator
USE WHEN a test intermittently fails on unchanged code. Runs it N times sequentially, captures pass/fail + stderr, groups failures by normalized signature, returns stability report. Read-only — never modifies code or installs deps. For statistical signal across runs, not one-shot diagnosis.
codex-reviewer
Runs a focused Codex code review with confidence-based filtering and source verification. Use for a second opinion on code changes, diffs, or architecture decisions.
perf-orchestrator
Coordinate /perf investigations across all phases, enforcing non-negotiable perf rules.
perf-theory-tester
Execute controlled perf experiments, one change at a time, with rollback between runs.
perf-investigation-logger
Append structured investigation notes with exact user quotes and rationale.