A publishing checklist that reviews drafts, fills page details, and sends content to a connected content management system as a draft.

Use it to prepare drafts, write the URL slug, search-result title and description, send content to the CMS, and publish when permission allows.

It catches missing sources, placeholders, links, FAQs, structured data, and other issues before content is handed to the site.

publish — Skill for Claude Code and Codex by ai-search-guru

Install

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.

Any agent

npx skills add ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool --skill publish

Clone the repo

git clone --depth 1 https://github.com/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/publish/github.svg)](https://agentmods.dev/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/publish)

Your own site

<a href="https://agentmods.dev/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/publish"><img src="https://agentmods.dev/badge/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/publish/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/publish"><img src="https://agentmods.dev/badge/skills/ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 640 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00023	$0.00640
Opus 5.5	$0.00009	$0.00256
Sonnet 5.5	$0.00005	$0.00128
Haiku 4.5	$0.00002	$0.00064

Measured yesterday against content hash 6cb7e599f9e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

publish 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 yesterday.

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.

skills/publish/SKILL.md · 41 lines

How it starts

The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ready to publish

Get drafts ready to go live: check them, fill their page fields, hand them to the site's CMS as drafts, and publish them. The app decides whether a page goes live: it asks the person unless an Admin allowed this agent to go live on its own.

When to use

"Get the 2 ready drafts published", "Is this draft ready to go live?", "Fill the SEO fields for this page."

What to read

list_drafts: the brand's drafts and their status; the ready ones first.
get_draft for each draft, at most three in one run: its passages, where it is live, and the suggestions still waiting for review.
list_connections: whether the brand has a CMS site connected.
get_site_audit_summary, then list_site_audit_issues, when the page is live already: what its latest audit failed.

Steps

Check each draft: suggestions still waiting, links without an address, claims without a source, a missing FAQ or schema, figures that need a date, [placeholders] still in the text.
Fill the page fields: the URL slug, the SEO title (about 60 characters) and the meta description (about 155 characters), from the draft's own words.
Hand it to the CMS as a draft. If a tool that sends a draft to the site's CMS is offered to you, send the draft; the app asks the person first unless this agent may go live on its own. Otherwise the person uses Send to CMS in the Content Library. A draft isn't live.
Publish only when the person asked for the page to go live, and only a new page: one that is live already is changed in the Content Editor. If a tool that publishes a page is offered to you (Webflow, WordPress or Wix; Framer publishes the whole site, so the person publishes it there), use it once the checks pass. If this agent may go live on its own, the app publishes once its own checks pass too; otherwise the person clicks. Never say a page is live before the app says so.

Output

For each draft: Ready or Not ready, the checks that failed and how to fix them, and the page fields in a small table (Field, Value). Then the next step: Send to CMS, then Publish, and whether it waits for the person's click.

Read the full file on GitHub · 41 lines

Changes

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.

yesterday First seen · 41 lines · 23 tokens per session scan A 6cb7e599f9e6

Subscribe to this mod's changes

publish is a skill published in the GitHub repository ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool (449 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 640 once invoked, about $0.0001 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-11-05.

Marketing and SEO Writing and docs ai-search-optimization answer answer-engine-optimization chatgpt claude generative-engine-optimization

publish next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
publishai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool	Skill	449	yesterday	MIT	A	23	Claude Code, Codex
geo-platform-optimizerasale-ai/seo-geo-skill	Skill	6	2mo ago	none	A	34	Claude Code
ansvisor-aeo-coach-standaloneansvisor/ansvisor	Skill	232	yesterday	MIT	A	148	Claude Code, Codex
geo-loopmverab/eGEOagents	Skill	217	yesterday	MIT	A	62	Claude Code
content-scoringmverab/eGEOagents	Skill	217	yesterday	MIT	A	34	Claude Code
competitive-analysismverab/eGEOagents	Skill	217	yesterday	MIT	A	29	Claude Code
schema-generatormverab/eGEOagents	Skill	217	yesterday	MIT	A	35	Claude Code