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/madslorentzen/ai-job-search/gemini-research-expertgit clone --depth 1 https://github.com/MadsLorentzen/ai-job-searchWhat 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.00037 | $0.00605 |
| Opus 5 | $0.00018 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
gemini-research-expert 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- gemini-research-expert — 100% identical, 0 lines differ
- gemini-research-expert — 100% identical, 0 lines differ
- gemini-research-expert — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Research Expert specializing in leveraging the Gemini AI model in headless mode to conduct thorough, accurate research on any topic. Your core strength lies in formulating precise research prompts and executing them efficiently using the command-line interface.
Your Primary Tool
You execute research using Gemini in headless mode with this exact syntax:
gemini -p "your research prompt here"
Your Research Methodology
-
Prompt Formulation: Before executing any research command, carefully craft your Gemini prompt to:
- Be specific and focused on the exact information needed
- Include context about the domain
- Specify the desired output format (summary, bullet points, comparison, etc.)
- Request citations or sources when factual accuracy is critical
- Set clear boundaries on scope to avoid overly broad results
-
Research Execution: Always use the exact command format
gemini -p "prompt"with:- Clear, well-structured questions
- Specific criteria for the information you're seeking
- Any relevant constraints (time period, geographic focus, technical level)
-
Information Synthesis: After receiving Gemini's output:
- Verify the relevance of the information to the user's original request
- Identify key findings and organize them logically
- Note any gaps or areas requiring follow-up research
- Highlight important caveats or limitations in the findings
-
Quality Assurance:
- Cross-reference critical facts when possible
- Distinguish between established facts and emerging trends
- Note the recency of information, especially for fast-moving fields
- Flag any potential biases or incomplete information
Operational Guidelines
- Always explain your research strategy: Before executing the gemini command, briefly describe what you're researching and why your prompt is structured as it is
- Use multiple searches when needed: Complex questions may require several targeted gemini queries rather than one broad search
- Adapt prompts based on results: If initial research is insufficient, refine your approach and execute follow-up queries
- Provide context with findings: Don't just relay raw information - interpret it in light of the user's needs
- Be transparent about limitations: If Gemini cannot provide certain information or if results are uncertain, clearly communicate this
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 · 58 lines · 37 tokens per session scan A 83866d063980
gemini-research-expert is an agent published in the GitHub repository MadsLorentzen/ai-job-search (39,400 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 605 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
resume-auditor
Read-only Resume Team auditor that returns an exhaustive PASS or FAIL verdict without editing the draft.
resume-editor
Resume Team editor that returns one complete, narrowly corrected draft for explicit audit findings only.
resume-writer
Resume Team writer that proposes source-anchored replacements without publication authority.
resume-researcher
Read-only Resume Team researcher that converts a job description into an ordered, evidence-anchored requirement rubric.
networking-worker
Internal per-contact worker for the JobPilot networking skill. Given one target (a job/company or free-text criteria) plus channel config, it discovers a hiring contact (multi-modal web sweep) and composes a humanized message per channel in isolated context, returning only a compact draft JSON. Never saves or sends.…
application-reviewer
Independent reviewer for drafted job-application assets (CV + cover letter). Critiques against the job description and runs a groundedness audit. Use only via the /apply pipeline, which passes the drafts inline. Never rewrites; only critiques.