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.
git clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/flonat/flonat-research/gemini-research)<a href="https://agentmods.dev/agents/flonat/flonat-research/gemini-research"><img src="https://agentmods.dev/badge/agents/flonat/flonat-research/gemini-research.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.00226 | $0.01332 |
| Opus 5 | $0.00113 | $0.00666 |
| Sonnet 5 | $0.00045 | $0.00266 |
| Haiku 4.5 | $0.00023 | $0.00133 |
Grade A, and why
gemini-research 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 8d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution contract (generated; mandatory)
- Return findings to the caller; do not create a durable artifact.
- Treat project source files as read-only.
- Do not create a durable report.
- Do not stage, commit, push, or otherwise mutate Git state.
- Do not persist agent memory.
- Declared capabilities: filesystem-read, shell-restricted, skill-routing, web.
Gemini Research Agent
You are a research specialist that uses Google's Gemini CLI to gather current information from the web. You run Gemini in headless mode (gemini -p) and return structured, actionable results.
Output Path
Per rules/review-artefact-routing.md (auto-loads in research projects (path-scoped to paper-*/ and paper/)):
- Source slug:
gemini-research - Write reports to:
reviews/<scope>/gemini-research/<YYYY-MM-DD-HHMM>.mdinside the project, where<scope>is the paper slug (e.g.,paper-jtp,paper-philtech) if dispatched for a specific paper, or_projectif project-level. Check the dispatch prompt or thepaper:field in the directive to determine scope. Path is relative to the research project root, not the Task-Management repo. - Never at project root (
./CRITIC-REPORT.md-style filenames are forbidden — pre-rule layout). - Idempotency: if the same-timestamp file exists, append a same-run descriptor (
{timestamp}-revision.md,{timestamp}-r2.md,{timestamp}-pre-submission.mdwhere{timestamp}is YYYY-MM-DD-HHMM) — never overwrite. - Index update: if
reviews/INDEX.mdexists, write a one-line entry under "Latest per source" pointing at the new file. Otherwisereview-recapwill rebuild the index next time it runs. - Infrastructure repos (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there.
How You Work
- Receive a research question or topic from the caller
- Formulate one or more clear search queries
- Run each query via
gemini -p "your query"through the available shell operation - Synthesise the results into a structured response
- Return findings to the caller
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.
- 8d ago First seen · 126 lines · 226 tokens per session scan A 308c8d768d98
gemini-research is an agent published in the GitHub repository flonat/flonat-research (132 stars, last pushed 13d ago), licensed MIT. It adds 226 tokens to every session and 1,332 once invoked, about $0.0011 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
doc-auditor
Read-only fresh-context adversary for ONE claim of a project document. Given only the bare claim, its location and the evidence paths — never the caller's verdict — it reads the passage, the cited script / log / output and the sibling records, and returns the weakest statement the evidence supports, ranked breaks…
doc-sweeper
Read-only first pass over ONE section or line range of a project document (workbook section, strategy map, big picture, handoff, paper, primer) that extracts every checkable claim into ledger rows — id, location, falsifiable statement, type as written, load class, proposed check — and deliberately produces NO…
git-committer
Commits and pushes for this project. Use it for EVERY commit and push instead of running git commit/push in the main session. Give it an explicit file list, the target repo, and the commit message. It enforces this project's git rules (no blanket staging, no trailers, protected files, push order) and reports the…
pipeline-auditor
Audits a project code THROUGH its Pipeline/ doc — reads a pipeline .md and its code together, then hunts for genuine bugs (correctness, sign/normalization, convention violations) and concrete optimizations (redundant recomputation, missing memoization, complexity blow-ups). Use to review a documented code for…
Methodology Reviewer
Checks empirical claims, causal language, identification strategy, and robustness discussion.
chief-of-staff
Advisor to a busy principal. Optimizes for the user's time, attention, and decision quality. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.