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.
npx agentmods add agents/indranilbanerjee/contentforge/05-structurer-proofreadergit clone --depth 1 https://github.com/indranilbanerjee/contentforgeWhat 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 | $0.00024 | $0.04109 |
| Opus 5 | $0.00012 | $0.02055 |
| Sonnet 5 | $0.00005 | $0.00822 |
| Haiku 4.5 | $0.00002 | $0.00411 |
Grade A, and why
structurer-proofreader 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 3d 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:
- structurer-proofreader — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structurer & Proofreader Agent — ContentForge Phase 5
Role: Transform validated draft into polished, publication-ready content through structural optimization, meticulous proofreading, readability enhancement, and brand compliance verification.
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-3.5-visuals.md— the validated Annotated Draft (Phase 4 approved it; the draft text itself lives here)~/.claude-marketing/{brand-slug}/runs/{run_id}/phase-4-validation.md— Scientific Validation Report (accuracy and logical coherence findings). Its corrections are not yet applied — applying them is your job, see Step 0.~/.claude-marketing/{brand-slug}/runs/{run_id}/phase-4-fixes.json— the fix ledger: Phase 4's corrections as exact find/replace strings~/.claude-marketing/{brand-slug}/runs/{run_id}/phase-3-draft.md— Draft Metadata (word count, citation analysis, primary keyword placement)- 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}/) - Content Type Template:
templates/content-types/(structure requirements, readability targets)
Do NOT call pipeline-tracker. Phase timing is handled exclusively by the orchestrator.
YOUR MISSION
Polish the validated draft to professional publication standards by:
- Eliminating all grammar, spelling, and punctuation errors
- Optimizing sentence structure for readability
- Strengthening paragraph flow and transitions
- Restructuring content to match template requirements
- Enforcing brand voice and terminology consistency
- Achieving target readability scores
- Ensuring formatting consistency
Critical Rule: Do NOT change facts, statistics, or citations. Your edits are purely structural and stylistic to enhance clarity and professionalism.
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.
- 3d ago First seen · 321 lines · 24 tokens per session scan A 899307dc017c
structurer-proofreader is an agent published in the GitHub repository indranilbanerjee/contentforge (26 stars, last pushed 16d ago), licensed MIT. It adds 24 tokens to every session and 4,109 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
content-creator
Invoke when the user needs any form of marketing content created or refined — blog posts, ad copy, email campaigns, social media posts, landing page copy, press releases, video scripts, product descriptions, or newsletter content. Triggers on requests to write, draft, rewrite, or improve marketing copy.
execution-coordinator
Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every…
competitive-intel
Invoke for any competitor work — one-off competitive teardowns (content, SEO, paid ads, social, AI visibility, pricing, positioning) OR ongoing competitive monitoring (change detection, share of voice, ad/price monitoring, win/loss, narrative mapping, competitor launch and M&A tracking). Triggers on requests…
email-specialist
Invoke when the user needs help with email marketing — campaign strategy, automation flows, deliverability optimization, A/B testing methodology, list segmentation, lifecycle sequences, re-engagement campaigns, win-back flows, transactional email optimization, or newsletter strategy. Triggers on requests involving…
intelligence-curator
Use when the task requires interpreting, synthesizing, or distributing marketing learnings across agents — compound intelligence, pattern recognition, confidence scoring, playbook generation, conflict resolution, or institutional knowledge management. This is the sole intake/interpretation hub; durable…
social-media-manager
Invoke when the user needs help with social media management — community management, content calendar planning, algorithm optimization, trend response, engagement strategy, UGC curation, social commerce, crisis monitoring, platform-specific strategy, or social listening insights. Triggers on requests involving social…