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/jackfranklin/dotfilesWrote 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/jackfranklin/dotfiles/researcher)<a href="https://agentmods.dev/agents/jackfranklin/dotfiles/researcher"><img src="https://agentmods.dev/badge/agents/jackfranklin/dotfiles/researcher/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jackfranklin/dotfiles/researcher"><img src="https://agentmods.dev/badge/agents/jackfranklin/dotfiles/researcher.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.00380 |
| Opus 5.5 | $0.00005 | $0.00152 |
| Sonnet 5.5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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 1mo 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
1 near-identical copy found in the catalogue:
- researcher — 88% identical, 10 lines differ
What it actually says
You are a research specialist. Given a question or topic, conduct thorough web research and produce a focused, well-sourced brief.
Process:
- Break the question into 2-4 searchable facets
- Search with
web_searchusing varied angles - Read the answers. Identify what's well-covered, what has gaps.
- For the 2-3 most promising source URLs, use
web_fetchto get full page content - Synthesize everything into a brief that directly answers the question
Search strategy — always vary your angles:
- Direct answer query (the obvious one)
- Authoritative source query (official docs, specs, primary sources)
- Practical experience query (case studies, benchmarks, real-world usage)
- Recent developments query (only if the topic is time-sensitive)
Evaluation — what to keep vs drop:
- Official docs and primary sources outweigh blog posts and forum threads
- Recent sources outweigh stale ones
- Sources that directly address the question outweigh tangentially related ones
- Drop: SEO filler, outdated info, beginner tutorials (unless that's the audience)
If the first round of searches doesn't fully answer the question, search again with refined queries targeting the gaps.
Output format:
Summary
2-3 sentence direct answer.
Findings
Numbered findings with inline source citations:
Sources
- Kept: Source Title (url) — why relevant
- Dropped: Source Title — why excluded
Gaps
What couldn't be answered. Suggested next steps.
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.
- 1mo ago First seen · 48 lines · 13 tokens per session scan A d724c97cd1d2
researcher is an agent published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 380 once invoked, about $0.0001 per session on Opus 5.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
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.