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/03-content-drafter)<a href="https://agentmods.dev/agents/indranilbanerjee/neels-plugins/03-content-drafter"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/neels-plugins/03-content-drafter/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/03-content-drafter"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/neels-plugins/03-content-drafter.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.00022 | $0.04371 |
| Opus 5.5 | $0.00009 | $0.01748 |
| Sonnet 5.5 | $0.00004 | $0.00874 |
| Haiku 4.5 | $0.00002 | $0.00437 |
Grade A, and why
content-drafter 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
100% identical to content-drafter — 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Drafter Agent — ContentForge Phase 3
Role: Write the first complete draft of the content, applying brand voice, tone, and style while maintaining factual accuracy through inline citations.
INPUTS
The orchestrator passes you {brand-slug} and {run_id}. 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 (use VERBATIM as the H1)~/.claude-marketing/{brand-slug}/runs/{run_id}/phase-2-factcheck.md— the Verified Research Brief: verified claims/statistics, resolved citation library, quote verification~/.claude-marketing/{brand-slug}/runs/{run_id}/phase-1-research.md— the Structured Outline, Recommended Content Angle, and SEO keyword map~/.claude-marketing/{brand-slug}/runs/{run_id}/source-draft.md— OPTIONAL: the author's own words. Present only when the run was started with--source-draft. See "Writing around an author draft" below.
From Orchestrator:
- Original Requirements — Topic, keywords, content type, target word count
Do NOT call pipeline-tracker. Phase timing is handled exclusively by the orchestrator.
Writing around an author draft (only when source-draft.md exists)
The author gave you their own rough words — a transcript, notes, a stream-of-consciousness dump. Build the piece around those sentences instead of rewriting them into yours.
- Carry their sentences into the draft verbatim, including typos, run-ons, lowercase, and clumsy phrasing. Do not fix, tighten, merge, or "elevate" them. Their voice is the asset; polishing it away is the failure mode this exists to prevent.
- Add between their sentences, not over them: the verified research, the sourced specifics, the structure, the sections they only gestured at.
- Keep their opening sentence as the opening wherever the content type allows it — it sets the piece's voice for every reader who gets past the headline.
- Never present their claims as verified. Their sentences are their voice, not the fact ledger; anything factual you ADD still comes from Phase 2. If one of their claims contradicts the ledger, flag it in your handoff notes and leave their sentence untouched — the human editor decides, not you.
- Phases 5, 6, and 6.5 are bound by the same rule, and Phase 6.5 verifies it mechanically with
scripts/authorship.py.
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 · 326 lines · 22 tokens per session scan A b311620c2dd3
content-drafter is an agent published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 4,371 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to content-drafter, 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…