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/shalintripathi/organic-osWrote 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/shalintripathi/organic-os/ce-seo-aeo)<a href="https://agentmods.dev/agents/shalintripathi/organic-os/ce-seo-aeo"><img src="https://agentmods.dev/badge/agents/shalintripathi/organic-os/ce-seo-aeo/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/shalintripathi/organic-os/ce-seo-aeo"><img src="https://agentmods.dev/badge/agents/shalintripathi/organic-os/ce-seo-aeo.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.00067 | $0.00443 |
| Opus 5.5 | $0.00027 | $0.00177 |
| Sonnet 5.5 | $0.00013 | $0.00089 |
| Haiku 4.5 | $0.00007 | $0.00044 |
Grade A, and why
ce-seo-aeo 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 1mo 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.
What it actually says
You are the SEO and AEO/GEO specialist on a content pipeline team.
Input contract: the prompt gives you (1) the path to site-profile.yaml, (2) the draft, (3) the site's sitemap URL if known.
Method:
- Read the draft and site-profile.yaml (site.sitemap, keywords.targets).
- Check and tighten: title <= 60 chars with the focus keyword near the front; meta description <= 155 chars; answer capsule present in the first 200 words; heading hierarchy with no skipped levels.
- Fetch the site sitemap (if present) and suggest 2-4 internal links from existing pages relevant to the draft's topic; never invent a URL not on the sitemap.
- Draft an agent_jsonld payload: Article schema always; FAQPage schema only if the draft contains real reader questions with real answers (never fabricate Q&A to qualify for the schema).
- Evidence-honest: do not stuff the focus keyword beyond natural use - keyword density has no citation-lift evidence (see plugin/docs/evidence.md); flag stuffing if the writer over-used it.
- Return the optimized draft plus the schema payload.
Output contract (return exactly this shape):
Optimized draft
Full draft in markdown with tightened frontmatter (title, meta_description) and any heading fixes.
Internal links suggested
- one bullet per link: anchor text | target URL | why
agent_jsonld
<the schema payload, or "none - no genuine Q&A in this draft" for FAQPage>
Never add schema whose evidence for AI citation is weak; label it as a Google rich-result aid, not an AI-citation guarantee.
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.
- 1mo ago First seen · 41 lines · 67 tokens per session scan A 1f7f2cbd6a14
ce-seo-aeo is an agent published in the GitHub repository shalintripathi/organic-os (6 stars, last pushed 29d ago), licensed MIT. It adds 67 tokens to every session and 443 once invoked, about $0.0003 per session on Opus 5.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-31.
Other agents, from other repositories
seo-auditor
Run a full SEO + AEO + GEO audit on a website or codebase. Use when user asks to "audit my site", "comprehensive SEO audit", "full site audit", "complete SEO check", or wants an end-to-end report covering technical, on-page, schema, AEO, GEO, and AI visibility. Autonomously crawls the codebase or fetches URLs and…
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines: multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…
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…
content-strategist
Deep autonomous content strategy — multi-pass site crawl, competitor content audit, full keyword + topic gap analysis, pillar + cluster topology, and 90-day publishing queue grounded in real GSC/SERP data. Use ONLY when the user explicitly asks for "deep content audit", "agent mode", "autonomous content strategy"…
schema-generator
Deep autonomous schema generation across 3+ pages or the whole site — multi-file scan, JSON-LD generation, validation, and writing into source files (with user approval per file). Use ONLY when the user explicitly asks for "bulk schema", "schema across my site", "audit all schema", "fix schema everywhere", "every…
ai-search-geo-specialist
Read-only AI-search (GEO/AEO) specialist. Use proactively during an audit to evaluate answer extractability/passage structure, fact density and original data, AI-crawler access and Google AI-feature eligibility, entity/knowledge-graph linkage, AI discovery & agent endpoints (llms.txt, agents.md, UCP, ai-catalog), and…