clippos-package

clippos-package is a command for coding agents from dylan-buck/Clippos. It costs 25 tokens per session (413 once invoked), scanned A, original, MIT.

A command that creates a publishing package for each approved video clip, including titles, thumbnails, captions, hashtags, and opening hooks.

In plain words
What is it for?
Generating and saving promotional text and visual-package details for approved video clips.
Why use it?
It turns rendered clips into ready-to-publish social-media materials instead of leaving those details to be prepared separately.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the clippos plugin — 1 skill, 3 commands shipped together

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.

agentmods
npx agentmods add commands/dylan-buck/clippos/clippos-package
Clone the repo
git clone --depth 1 https://github.com/dylan-buck/Clippos

Or install clippos, the plugin that ships this one along with the rest of its 1 skill, 3 commands.

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.

agentmods badge for clippos-package

README.md
[![agentmods](https://agentmods.dev/badge/commands/dylan-buck/clippos/clippos-package.svg)](https://agentmods.dev/commands/dylan-buck/clippos/clippos-package)
Your own site
<a href="https://agentmods.dev/commands/dylan-buck/clippos/clippos-package"><img src="https://agentmods.dev/badge/commands/dylan-buck/clippos/clippos-package.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 413 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00413
Opus 5 $0.00013 $0.00206
Sonnet 5 $0.00005 $0.00083
Haiku 4.5 $0.00003 $0.00041

Measured 4d ago against content hash 844bbd848f18, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clippos-package 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.

commands/clippos-package.md · 29 lines

What it actually says

Invoke the clippos skill's packaging workflow for: $ARGUMENTS

Resolve CLIPPOS_ROOT with the prologue documented in SKILL.md (env var > HERMES_SKILL_DIR > CLAUDE_PLUGIN_ROOT > ~/.hermes/skills/clippos

~/.claude/skills/clippos > ~/.codex/skills/clippos > newest plugin-cache checkout containing scripts/hermes_clippos.py > CLIPPOS_ROOT line in ~/.config/clippos/.env > $PWD). Each candidate must contain scripts/hermes_clippos.py. Run bash $CLIPPOS_ROOT/scripts/bootstrap-venv.sh; it is idempotent after a completed install and resumes incomplete .venv installs. Then resolve CLIPPOS_PYTHON to $CLIPPOS_ROOT/.venv/bin/python when executable, otherwise python3.

Resolve the target workspace (either the argument, or the most recent skill-jobs/*/jobs/<job_id>/ directory under the configured output dir). Then:

  1. Run package-prompt against the workspace to emit package-request.json.
  2. Read package-request.json, follow its package_prompt and response_schema, and write package-response.json beside the request.
  3. Run package-save to validate the response, fan per-clip package.json files into renders/<clip_id>/, and write the summary package-report.json.
  4. Return the per-clip pack paths plus the rendered MP4 paths they sit next to.
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.

  1. 4d ago First seen · 29 lines · 25 tokens per session scan A 844bbd848f18

Subscribe to this mod's changes

clippos-package is a command published in the GitHub repository dylan-buck/Clippos (9 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 413 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.