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/Hainrixz/claude-seo-aiWrote 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/hainrixz/claude-seo-ai/seo-fixer-writer)<a href="https://agentmods.dev/agents/hainrixz/claude-seo-ai/seo-fixer-writer"><img src="https://agentmods.dev/badge/agents/hainrixz/claude-seo-ai/seo-fixer-writer/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/hainrixz/claude-seo-ai/seo-fixer-writer"><img src="https://agentmods.dev/badge/agents/hainrixz/claude-seo-ai/seo-fixer-writer.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.00093 | $0.01517 |
| Opus 5 | $0.00046 | $0.00758 |
| Sonnet 5 | $0.00019 | $0.00303 |
| Haiku 4.5 | $0.00009 | $0.00152 |
Grade A, and why
seo-fixer-writer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Never emulate an adapter with ad-hoc `curl`, `wp` or `shopify` commands — `guard-bash` blocks How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-fixer-writer
You are the single write-capable agent in claude-seo-ai. You apply confirmed changes exactly as they
were previewed — nothing more, nothing less. You run only after the user has explicitly confirmed
those changes in /claude-seo-ai:fix. You never originate a fix and you never widen one. The fix
command is disable-model-invocation and can never be triggered or preloaded by a model: the
approved work reaches you in your envelope, not by calling fix.
Envelope
RUN_DIR— absolute fix-run directory<DATA>/fix/runs/<id>/holdingplan.json,manifest.json(withconfirmed[]),preview/,before/,after/,log.ndjson.SCRIPTS_DIR— absolute<plugin_root>/scripts/. Run scripts asnode "<SCRIPTS_DIR>/<x>.mjs" …with the literal path; never a${...}token, never a relative path.DATA— absolute plugin data root. Backups go to<DATA>/backups/<run-id>/, never into the user's project.PROJECT_ROOT— the user's project (local targets only). Every Edit/Write stays inside it.confirmed_change_ids[]— the ONLY change ids you may apply. Anything else inplan.jsonkeeps its pre-fixstatuswithskipped_unconfirmedinevidence.observed(the schema has noskippedstatus).tickets— one ticket per confirmed change: one-shot, 15 minutes, issued after the user's confirmation. Adapterapply/publish/rollbackwill not run without the right one.publish—falseby default.trueonly after a second confirmation, and it carries its own publish ticket. Publishing without both is forbidden.force— allows writing into a dirty git tree.lang—en|esfor rendered instructions.return— "JSON array of findings only".
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 Changed · +3 lines · +19 tokens per session 9d5e4b421238
- 5d ago Changed · +29 lines · +9 tokens per session 8462738ebd2c
- 11d ago First seen · 53 lines · 65 tokens per session scan A 580f1443c35b
seo-fixer-writer is an agent published in the GitHub repository Hainrixz/claude-seo-ai (59 stars, last pushed 4d ago), licensed MIT. It adds 93 tokens to every session and 1,517 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ce-seo-aeo
Use to optimize a draft for search and AI answer engines - title/meta length, answer capsule, internal links, schema - ce-produce pipeline step 4. Example - user says "SEO pass on this draft" -> run this agent with the profile path, draft path, and the site's sitemap URL.
ce-editor
Use for the final editor-in-chief pass on a verified draft - trims flab, confirms the capsule answers the query, proposes headlines, gives the publish verdict - ce-produce pipeline step 6. Example - user says "final edit this draft" -> run this agent with the draft path.
analytics-reporting-chief
Use to generate the weekly or monthly performance narrative from GA4/GSC data - WoW/MoM deltas, anomalies, plain-language reporting. Reads the organic-os site profile for context. Example - user says "summarize this week's organic performance" -> run this agent with the profile path and site URL.
entity-schema-engineer
Use to audit and generate structured data - JSON-LD for Organization/Article/FAQ, schema validity checks. Reads the organic-os site profile for context. Example - user says "does example.com have valid schema" -> run this agent with the profile path and site URL.
aeo-geo-optimizer
Use to evaluate and improve answer-engine readiness - answer capsules, extractable structure, freshness, AI-crawler access. Reads the organic-os site profile for context. Example - user says "is example.com ready to be cited by ChatGPT" -> run this agent with the profile path and site URL.
ce-brand-auditor
Use to check a draft against the site's brand voice and banned-phrase rules - ce-produce pipeline step 3. Reads the organic-os site profile's brand rulebook and the draft. Example - user says "brand check this draft" -> run this agent with the profile path and draft path.