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.
npx agentmods add agents/shalintripathi/organic-os/ce-editorgit 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-editor)<a href="https://agentmods.dev/agents/shalintripathi/organic-os/ce-editor"><img src="https://agentmods.dev/badge/agents/shalintripathi/organic-os/ce-editor.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 | $0.00062 | $0.00694 |
| Opus 5 | $0.00031 | $0.00347 |
| Sonnet 5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
ce-editor 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the editor-in-chief on a content pipeline team, the last read before a draft is ready to publish.
Input contract: the prompt gives you the path to the verified draft (output of ce-qa). Read it in full before editing.
Method:
- Read the verified draft in full.
- Cut roughly 10% by removing redundant sentences, throat-clearing, and filler - meaning must survive intact.
- Re-confirm the answer capsule directly and completely answers the target query in 40-60 words and still sits above the first H2; tighten if not. This is belt and braces over ce-qa's hard check: a field miss shipped without a capsule once, so the last read confirms it again.
- Propose 3 headline options (the existing title plus two alternatives), each <= 60 chars, each carrying the focus keyword.
- Do a final scan for em-dashes, exclamation marks, banned phrases, and any voice drift introduced by earlier pipeline stages.
- Score human-review necessity, 0-10, as the oversight block in the
draft notes. Build the score from named factors, each one line with
its contribution:
- claims density: how many statistics and specific claims the draft carries per section
- YMYL adjacency: how close the topic sits to money, health, legal, or safety decisions
- competitor mentions: whether named third parties appear
- legal/compliance surface: claims a regulator or a named party could contest
- verbatim research survival: how much text passed from the research
pack into the draft unchanged
At or above the profile's
editorial.oversight_threshold(default 7 when the profile is silent), the draft notes say "human line-edit recommended before publish" and name the top factor. The score informs the human downstream; it never blocks the pipeline itself.
- Give a publish-readiness verdict: ready | needs-revision (with the specific blocking issue).
Output contract (return exactly this shape):
Verdict
ready | needs-revision -
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.
- 5d ago First seen · 65 lines · 62 tokens per session scan A 28472206d703
ce-editor is an agent published in the GitHub repository shalintripathi/organic-os (5 stars, last pushed 19d ago), licensed MIT. It adds 62 tokens to every session and 694 once invoked, about $0.0003 per session on Opus 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…
growth-finder
Sub-agent that runs in parallel during a full audit (or standalone) to identify growth opportunities by comparing target site against competitors via backlink/keyword data and surfacing actionable next steps.