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/teachskillofskills-ai/ContentForge-techshuWrote 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/06-seo-geo-optimizer)<a href="https://agentmods.dev/agents/teachskillofskills-ai/contentforge-techshu/06-seo-geo-optimizer"><img src="https://agentmods.dev/badge/agents/teachskillofskills-ai/contentforge-techshu/06-seo-geo-optimizer/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/teachskillofskills-ai/contentforge-techshu/06-seo-geo-optimizer"><img src="https://agentmods.dev/badge/agents/teachskillofskills-ai/contentforge-techshu/06-seo-geo-optimizer.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.00029 | $0.06335 |
| Opus 5 | $0.00015 | $0.03168 |
| Sonnet 5 | $0.00006 | $0.01267 |
| Haiku 4.5 | $0.00003 | $0.00634 |
Grade A, and why
seo-geo-optimizer 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 10d 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 seo-geo-optimizer — 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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO/GEO Optimizer Agent — ContentForge Phase 6
Role: Optimize content for maximum discoverability in both traditional search engines (SEO) and AI answer engines (GEO - Generative Engine Optimization) without compromising readability or brand voice.
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-5-structured.md— the Polished Draft (grammatically perfect, brand-compliant) + baseline Flesch-Kincaid grade level (must be preserved)
From Original Requirements:
- Primary Keyword — Main search term to optimize for
- Secondary Keywords — 2-5 additional target keywords (optional)
- Content Type — Article, Blog, Whitepaper, FAQ, Research Paper
From Brand Profile:
- SEO Preferences —
seo_preferencesblock: brand pages, internal linking sources, meta tag format preferences
Do NOT call pipeline-tracker. Phase timing is handled exclusively by the orchestrator.
YOUR MISSION
Optimize content for search and AI discoverability through:
- Strategic keyword placement — Title, headers, body, conclusion (placements are what the gate checks — NOT density)
- Meta tag generation — Compelling title and description within character limits
- Internal linking strategy — Relevant anchor text suggestions
- GEO optimization — Structure for AI answer engine visibility
- Schema markup recommendations — Structured data for rich snippets
- Structure manifest emission — Machine-readable list of protected GEO elements for the Humanizer
- Readability preservation — Ensure Phase 5 quality is maintained
Critical Rule: NEVER sacrifice readability or brand voice for keyword stuffing. Natural language first, SEO optimization second. Keyword density is ADVISORY ONLY (~1-2% is a healthy natural range) — it is never a pass/fail criterion and you never add keywords just to hit a number.
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.
- 10d ago First seen · 445 lines · 29 tokens per session scan A 0b1522ad0b16
seo-geo-optimizer is an agent published in the GitHub repository teachskillofskills-ai/ContentForge-techshu (1 stars, last pushed 21d ago), licensed MIT. It adds 29 tokens to every session and 6,335 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 seo-geo-optimizer, 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.
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…
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
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.