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/contentforgeWrote 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/contentforge/01-researcher)<a href="https://agentmods.dev/agents/indranilbanerjee/contentforge/01-researcher"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/contentforge/01-researcher.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.00026 | $0.04865 |
| Opus 5 | $0.00013 | $0.02433 |
| Sonnet 5 | $0.00005 | $0.00973 |
| Haiku 4.5 | $0.00003 | $0.00487 |
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 7d 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 — 100% identical, 0 lines differ
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.
- 7d ago First seen · 473 lines · 26 tokens per session scan A 290ca304e3de
researcher is an agent published in the GitHub repository indranilbanerjee/contentforge (26 stars, last pushed 20d ago), licensed MIT. It adds 26 tokens to every session and 4,865 once invoked, about $0.0001 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
ai-search-geo-specialist
Read-only AI-search (GEO/AEO) specialist. Use proactively during an audit to evaluate answer extractability/passage structure, fact density and original data, AI-crawler access and Google AI-feature eligibility, entity/knowledge-graph linkage, AI discovery & agent endpoints (llms.txt, agents.md, UCP, ai-catalog), and…
schema-generator
Structured-data specialist. Use proactively during an audit to validate existing JSON-LD and PROPOSE complete Tier-1 schema blocks (plus e-commerce/local schema and agentic-commerce readiness when those verticals are active). It proposes diffs only and does NOT write files.
content-eeat-analyst
Read-only content quality specialist. Use proactively during an audit to evaluate E-E-A-T (author identity, credentials, trust signals, transparency) and content freshness/temporal signals.
seo-fixer-writer
The ONLY agent allowed to write files. Used exclusively by the fix skill (the /claude-seo-ai:fix command) AFTER the user has confirmed the changes. Applies confirmed AUTO-class fixes (and PROPOSED ones the user accepted), backs up first, is idempotent, git-aware, and re-verifies each change.
technical-auditor
Read-only technical SEO specialist. Use proactively during an audit to analyze crawlability, indexability, rendering, Core Web Vitals, mobile-friendliness, title/meta/head hygiene, heading structure, social cards, images, internal linking, sitemaps, and (on multilingual sites) hreflang.
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…