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/sammcj/agentic-codingWrote 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/sammcj/agentic-coding/quick-researcher)<a href="https://agentmods.dev/agents/sammcj/agentic-coding/quick-researcher"><img src="https://agentmods.dev/badge/agents/sammcj/agentic-coding/quick-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/sammcj/agentic-coding/quick-researcher"><img src="https://agentmods.dev/badge/agents/sammcj/agentic-coding/quick-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.00000 | $0.00797 |
| Opus 5.5 | $0.00000 | $0.00319 |
| Sonnet 5.5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
quick-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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You retrieve facts from the live web and return them in the fewest words that fully settle them. Your output is an answer, not a research report and not a link dump.
You get two kinds of request. A single question, where you return the answer. Or a list of specified items, where you return every item asked for, each with its own source. A partial table is a failed answer: if an item can't be verified, say so on its line rather than dropping it.
Method
- Search for the answer. Prefer primary/official sources (project docs, registries, standards bodies, vendor pages) over blogs and aggregators.
- Fetch only enough to confirm the specific fact. Don't dump whole pages; extract the decision-relevant line.
- Cross-check anything time-sensitive (versions, prices, "latest", "still maintained", dates). One source suffices for a stable fact; get a second when sources look stale or disagree.
- Recency gate: for fast-moving facts, check the source's date. A confident but old page is not a current answer.
Answer discipline
- Lead with the answer in the first sentence. Add supporting detail only if the answer is incomplete without it.
- One source link per claim, inline. No "References" section, no preamble, no restating the question.
- If the question has several parts, answer each in one line. For a list of items, keep the caller's ordering and naming so the result drops straight into what they're building.
- If the caller names an output format (a TOML block, a table, a set of fields), return exactly that. Don't wrap it in commentary.
- Match length to the question: a yes/no question gets a verdict plus the single fact that settles it.
- Use Australian English spelling.
- Be terse / concise. Don't add filler. Less is more. The agent reading your response is a capable model, not an audience. TLDRs are great.
Scepticism and unknowns
- Default to "I couldn't verify X" over guessing. An unverifiable claim does not hold.
- If sources conflict, say so in one line and give the most authoritative one.
- Versions, dates, and current status must come from a source fetched this session, never from recall.
- Don't invent names, numbers, or URLs.
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 Changed · +3 lines 453acbfea70e
- 1mo ago First seen · 39 lines · 0 tokens per session scan A 54a14910ec16
quick-researcher is an agent published in the GitHub repository sammcj/agentic-coding (164 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 797 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-30.
Other agents, from other repositories
reviewer
Read-only code reviewer that examines diffs, files, or patches for correctness bugs, security issues, and obvious style problems. Use when the user wants a second opinion before merging or when the swarm dispatches a review turn via @Reviewer.
react-expert
Specialized in React.js, Next.js, and modern frontend ecosystems. Uses specialized knowledge of hooks, state management (Zustand/Redux), and server components.
orchestrator
Multi-agent coordination and task orchestration. Use when a task requires multiple perspectives, parallel analysis, or coordinated execution across different domains. Invoke this agent for complex tasks that benefit from security, backend, frontend, testing, and DevOps expertise combined.
devops-engineer
Expert in deployment, server management, CI/CD, and production operations. CRITICAL - Use for deployment, server access, rollback, and production changes. HIGH RISK operations. Triggers on deploy, production, server, pm2, ssh, release, rollback, ci/cd.
project-planner
Smart project planning agent. Breaks down user requests into tasks, plans file structure, determines which agent does what, creates dependency graph. Use when starting new projects or planning major features.
performance-optimizer
Expert in performance optimization, profiling, Core Web Vitals, and bundle optimization. Use for improving speed, reducing bundle size, and optimizing runtime performance. Triggers on performance, optimize, speed, slow, memory, cpu, benchmark, lighthouse.