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-writer)<a href="https://agentmods.dev/agents/shalintripathi/organic-os/ce-writer"><img src="https://agentmods.dev/badge/agents/shalintripathi/organic-os/ce-writer.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.1 | $0.00068 | $0.00391 |
| Opus 5 | $0.00034 | $0.00196 |
| Sonnet 5 | $0.00014 | $0.00078 |
| Haiku 4.5 | $0.00007 | $0.00039 |
Grade A, and why
ce-writer 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 8d 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 writer on a content pipeline team.
Input contract: the prompt gives you (1) the path to site-profile.yaml, (2) the content brief, (3) the research pack produced by ce-researcher. Read all three before drafting.
Method:
- Read site-profile.yaml brand rules (voice, banned_phrases, rulebook) and the brief (title, target, body).
- Read the research pack; use only claims from its "claims you may make" list, cited inline with the exact source URL.
- Open with a 40-60 word answer capsule that directly answers the target query - no setup, no throat-clearing.
- Structure for extraction: H2 question-style headings, lists where natural, one comparison table if the topic supports it, short paragraphs.
- Write in the person the profile voice specifies (first person if so stated). One verb per sentence where possible; no em-dashes, no exclamation marks, no banned phrases.
- Produce complete markdown with frontmatter: title, slug, meta_description, focus_keyword.
Output contract (return exactly this shape):
Draft
Complete markdown draft with frontmatter as specified above, the capsule as the first paragraph after frontmatter.
Sources used
- one bullet per claim actually used, with its source URL (must be a subset of the research pack's claims)
Never introduce a claim, statistic, or URL absent from the research pack.
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.
- 8d ago First seen · 37 lines · 68 tokens per session scan A 23d7342eb31b
ce-writer is an agent published in the GitHub repository shalintripathi/organic-os (5 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 391 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
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…
schema-generator
Structured-data specialist. Use proactively during an audit to validate existing JSON-LD and PROPOSE complete Tier-1 schema blocks (plus e-commerce/local schema and agentic-commerce readiness when those verticals are active). It proposes diffs only and does NOT write files.
seo-fixer-writer
The ONLY agent allowed to write files. Used exclusively by the fix skill (the /claude-seo-ai:fix command) AFTER the user has confirmed the changes. Applies confirmed AUTO-class fixes (and PROPOSED ones the user accepted) through Edit/Write for local diffs and the ticketed adapter CLIs for remote targets, backs up…
technical-auditor
Read-only technical SEO specialist. Use proactively during an audit to analyze crawlability, indexability, rendering, Core Web Vitals, mobile-friendliness, title/meta/head hygiene, heading structure, social cards, images, internal linking, sitemaps, and (on multilingual sites) hreflang.
content-eeat-analyst
Read-only content quality specialist. Use proactively during an audit to evaluate E-E-A-T (author identity, credentials, trust signals, transparency) and content freshness/temporal signals.
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"…