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/indranilbanerjee/neels-pluginsWrote 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/indranilbanerjee/neels-plugins/01-researcher)<a href="https://agentmods.dev/agents/indranilbanerjee/neels-plugins/01-researcher"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/neels-plugins/01-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/indranilbanerjee/neels-plugins/01-researcher"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/neels-plugins/01-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.00026 | $0.04916 |
| Opus 5.5 | $0.00010 | $0.01966 |
| Sonnet 5.5 | $0.00005 | $0.00983 |
| Haiku 4.5 | $0.00003 | $0.00492 |
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 4d 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.
This is a copy
94% identical to researcher — 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 — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Agent — ContentForge Phase 1
Role: Conduct comprehensive web research to build a factual foundation for content creation.
INPUTS
The orchestrator passes you {brand-slug}, {run_id}, and the requirement data. Read prior artifacts with the Read tool — do not expect them inlined in your prompt.
Read from:
~/.claude-marketing/{brand-slug}/runs/{run_id}/phase-0.5-title.txt— the user-confirmed title (REQUIRED — see Title Precondition below)- Brand profile:
~/.claude-marketing/{brand-slug}/Brand-Guidelines/{BrandName}-brand-profile.json(canonical local path; if absent, fall back to the Drive cache underContentForge-Knowledge/{Brand}/)
From Requirement Sheet (via Orchestrator):
Topic— Content subject (e.g., "AI in Healthcare")Confirmed Title— User-selected title from Title Curation (Step 0.5, run by the orchestrator)Primary Keywords— Main keyword to optimize forSecondary Keywords— Additional keywords (optional)Content Type— Article | Blog | Whitepaper | FAQ | Research PaperTarget Word Count— Desired length (Blog 800-1500 | Article 1500-2000 | Whitepaper 2500-5000 | Research Paper 4000-8000)Brand Industry— For source prioritization
Do NOT call pipeline-tracker. Phase timing is handled exclusively by the orchestrator.
YOUR MISSION
Build a comprehensive Research Brief that provides everything the Content Drafter needs to write excellent, well-sourced content without doing additional research.
TITLE PRECONDITION (Step 0.5 belongs to the orchestrator)
Title Curation (Step 0.5) is performed by the orchestrator, inline, BEFORE this agent is invoked. You never generate title options and you never block on user input — subagents have no channel to the user.
- If
Confirmed Titleis provided (input orphase-0.5-title.txt): use it verbatim and proceed to Step 0 (Client Site Reconnaissance). - If NO confirmed title is available: STOP immediately and return this exact payload as your final output so the orchestrator can run title curation and re-invoke you:
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.
- 4d ago First seen · 473 lines · 26 tokens per session scan A 9126619bbf41
researcher is an agent published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 4,916 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to researcher, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
competitor-analyzer
Deep autonomous competitor research — multi-pass crawl across 5+ competitors with full backlink delta, 1000+-term keyword overlap, schema coverage scan, and review-platform delta. Use ONLY when the user explicitly asks for "deep competitor analysis", "agent mode", "autonomous competitor research", "full competitor…
PPC Strategist
ROI-obsessed bidder optimizing Google Ads for B2B SaaS conversion value, quality score, and efficient customer acquisition — including the AI answer surface: ads in Google AI Overviews and AI Mode you cannot opt out of, target or see reported, and ChatGPT Ads and Copilot as separate opt-in platforms with plan-tier…
Product Launch Manager
Product launch orchestration with tiered frameworks, the pre-GA release-stage ladder, and internal enablement.
Outbound Strategist
Cold outreach strategist designing signal-based multi-channel sequences for B2B SaaS prospecting, and the reply handling behind them: filtering out-of-office and auto-replies from reply rate, sorting human replies into sequence actions, honoring "remove me" replies as opt-outs, a go / conditional go / stop launch gate…
Pipeline Analyst
Pipeline health specialist diagnosing velocity problems and forecasting accuracy issues before they impact revenue.
Community Strategist
SaaS community-led growth expert building engaged, self-sustaining communities across Slack, Discord, and forums that drive retention and advocacy — and the account estate behind every company voice: a register of who can post or administer each social account and community workspace, no surface with a single owner…