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/treymorgan/jobsearch-apply-mcp/gemini-research-expertgit clone --depth 1 https://github.com/treymorgan/jobsearch-apply-mcpWhat 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 today.
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.
This is a copy
100% identical to gemini-research-expert — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- today First seen · 58 lines · 37 tokens per session scan A 83866d063980
gemini-research-expert is an agent published in the GitHub repository treymorgan/jobsearch-apply-mcp (0 stars, last pushed 3d ago), 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. It is 100% identical to gemini-research-expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
job-worker
Internal per-job worker for JobPilot apply/score loops. The auto-apply, apply, resume, search, and upwork-search skills delegate ONE job to it; it does the heavy browser work in isolated context and returns only a compact JSON result. Not for direct user invocation.
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.…
job-lifecycle
The open/closed state of a job row, the four mechanisms that write closedat, and the filtering semantics that depend on it.
company-identity
How the catalogue decides that two postings name the same employer.
company-facets
The denormalized facet columns on companies — job-derived remoteregions and curated yc columns — their maintenance, and the separation between the two.
batch-scanner
Scans a single company's career portal for job openings. Spawned by the scan skill when processing multiple companies from a watchlist. Context: User has a watchlist of 10 companies and wants to scan all of them. user: "Scan all my companies" assistant: "[spawns batch-scanner for each company in portals.yml]" Use when…