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 skills add jxoesneon/Ciel --skill content-distribution-opsgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/skills/jxoesneon/ciel/content-distribution-ops)<a href="https://agentmods.dev/skills/jxoesneon/ciel/content-distribution-ops"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/content-distribution-ops/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/skills/jxoesneon/ciel/content-distribution-ops"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/content-distribution-ops.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.00023 | $0.00542 |
| Opus 5 | $0.00012 | $0.00271 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
content-distribution-ops 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
CIEL ADAPTATION: Content Distribution (The Social Layer)
This skill formalizes the lifecycle of public-facing content, from network optimization to platform-native distribution. it prioritizes voice integrity and signal-to-noise ratio.
Network Optimization (Connections)
- Reciprocity: Prioritize mutual follows over one-way connections.
- Prune Protocol: Surface inactive or "low-signal" accounts for review before unfollowing.
- Warm Paths: Use
lead-intelligenceto identify high-bridge targets aligned with current goals.
Content Engineering
- Atomic Claims: One post = one concrete claim or proof point. No engagement bait.
- Source-First: Derive content from real artifacts (code, memos, docs) via
brand-voice. - Hard Bans: Prohibit "Excited to share," "Game-changer," and generic "founder journey" filler.
Cross-Platform Adaptation
- X: Compressed, threaded, leading with the sharpest artifact.
- LinkedIn: Contextual expansion for non-niche audiences; professional but non-corporate tone.
- Threads/Bluesky: Direct and readable; avoid feed-gaming hashtags.
Operational Standards
- Approval Gate: ALL drafts must be presented to the user before publishing.
- Voice Fingerprint: Reuse the session's
VOICE PROFILEfor all adapted variants.
Anti-Patterns
- Verbatim Crosspost: Posting the exact same copy to X and LinkedIn (erodes platform authority).
- Fake Reflection: Adding a moral or "lesson learned" that wasn't in the source material.
- Amnesiac Outreach: Drafting a DM without referencing the existing connection context.
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 · 55 lines · 23 tokens per session scan A 3ba65d7fa949
content-distribution-ops is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 23 tokens to every session and 542 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
ai-native-software-dev
Use when the user asks to build, change, modernize, or reconstruct non-trivial software with an AI-native workflow, including greenfield development, work in an existing codebase, or authorized reference-based product reconstruction; also use when lifecycle planning, architecture, implementation, testing, review…
Code Quality Review
Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
redpolicy-guide
An editorial policy for turning webinar transcripts into self-contained guides. A transcript is a written record of spoken material, while a self-contained guide can be understood without watching the webinar.
write-overview
A workflow for researching and writing a review essay about a project topic when no finished source text exists. It gathers the facts, studies example essays when available and produces the article in a project output folder.