Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/teachskillofskills-ai/ContentForge-techshunpx agentmods add agents/teachskillofskills-ai/contentforge-techshu/05-structurer-proofreaderWrote 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/teachskillofskills-ai/contentforge-techshu/05-structurer-proofreader)<a href="https://agentmods.dev/agents/teachskillofskills-ai/contentforge-techshu/05-structurer-proofreader"><img src="https://agentmods.dev/badge/agents/teachskillofskills-ai/contentforge-techshu/05-structurer-proofreader.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.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 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.
This is a copy
100% identical to structurer-proofreader — 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 — 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.
- 7d ago First seen · 321 lines · 24 tokens per session scan A 899307dc017c
structurer-proofreader is an agent published in the GitHub repository teachskillofskills-ai/ContentForge-techshu (1 stars, last pushed 18d 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. It is 100% identical to structurer-proofreader, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.