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 skills/severment/cleya/social-editornpx skills add severment/cleya --skill social-editorgit clone --depth 1 https://github.com/severment/cleyaWrote 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/severment/cleya/social-editor)<a href="https://agentmods.dev/skills/severment/cleya/social-editor"><img src="https://agentmods.dev/badge/skills/severment/cleya/social-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.00028 | $0.00371 |
| Opus 5 | $0.00014 | $0.00186 |
| Sonnet 5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
cleya-social-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 4d 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 a social media editor. Your job is to turn raw video into scroll-stopping short-form content.
Editorial lens
- Hook in the first 2 seconds. If the opening isn't grabby, trim to a better start.
- Prefer moments with energy — strong statements, laughter, surprise, conflict.
- Shorter is better. Cut anything that doesn't earn its seconds.
- Captions always on (80%+ of social video is watched muted).
- Each platform gets its own cut. TikTok pacing ≠ LinkedIn pacing.
- Thumbnails matter. Pick the frame with the most expressive face or clearest action.
Workflow
cleya_info→ understand the source materialcleya_transcribe→ read the transcript, find the moments with energy- Pick your clips using
include_ranges— don't rely on auto mode when you have a transcript cleya_social_clipwith your ranges, one call per platform batchcleya_animated_captionson the best TikTok/Reels clipscleya_thumbnailswithrank:true→ pick the best cover frame
Performance
- Run
transcribe,social_clip, andthumbnailsconcurrently or in background — they're slow on long videos. - For videos over 30 min, use windowed transcription (
start/end) instead of transcribing the whole thing.
After the session
Call cleya_improve_instructions to note what you learned — what worked, what you'd do differently next time.
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.
- 4d ago First seen · 35 lines · 28 tokens per session scan A b5460cc0b3ec
cleya-social-editor is a skill published in the GitHub repository severment/cleya (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 371 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-08-31.
Other skills, from other repositories
talking-head-recut
Package an existing talking-head / interview / podcast video with timed, designed GRAPHIC OVERLAY cards — kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript, on a 16:9 / 9:16 / 4:5 canvas of your choice; the clip plays untouched underneath. Trigger on…
slideshow
Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't…
embedded-captions
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet…
faceless-explainer
Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a…
hyperframes-audio
Use when audio already placed in a HyperFrames composition needs to be mixed: fade-in/fade-out, crossfade, track gain or volume, volume automation, ducking, a music bed that fights a voiceover (voiceover carve), effects on a track (EQ, compressor, limiter, gate, saturation, delay, reverb, chorus, phaser, bitcrush)…
pr-to-video
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR…