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 45ck/skill-harness --skill demo-slideshow-editgit clone --depth 1 https://github.com/45ck/skill-harnessWrote 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/45ck/skill-harness/demo-slideshow-edit)<a href="https://agentmods.dev/skills/45ck/skill-harness/demo-slideshow-edit"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/demo-slideshow-edit/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/45ck/skill-harness/demo-slideshow-edit"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/demo-slideshow-edit.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.00060 | $0.00363 |
| Opus 5.5 | $0.00024 | $0.00145 |
| Sonnet 5.5 | $0.00012 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
demo-slideshow-edit 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 1mo 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
Demo Slideshow Edit
Overview
Use this skill when the best output is a curated still-frame or segment-based reel rather than a full narrated playback. The slideshow must remain source-backed and evidence-linked.
Inputs
- storyboard frames or screenshots
- selected spans from
video.shots.json,segment.evidence.json, orevents.json - source
.demo.yamlor QA flow/report - target duration, aspect ratio, and audience
Workflow
- Select frames or spans that show state changes clearly.
- Reject frames that expose secrets, private data, or unreadable UI.
- Define the sequence with durations, crop/zoom notes, and transition notes.
- Prefer simple transitions and stable framing over decorative effects.
- Record the source path, evidence links, and output path in the artifact manifest when available.
- Produce a render plan or command. Do not claim the MP4 is approved until evidence and safety checks pass.
Output
Return:
- source run directory
- ordered frame/span list
- duration and aspect ratio
- output media path
- review surface path, if generated
- checks needed before handoff
Guardrails
- Do not fabricate app states that were not captured.
- Do not crop away failures, warnings, or key context.
- Do not use external stock or music unless the user explicitly asks and licensing is recorded.
- Keep generated slideshow media out of git unless explicitly promoted.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 45 lines · 60 tokens per session scan A 193650d8ed69
demo-slideshow-edit is a skill published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 363 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
harness-init-runner
Initialize a lightweight repo-local Node.js harness (harness/ + .harness/) WITHOUT AIOS dependency. Use ONLY when you need a standalone, portable harness. If AIOS is installed, use aios-long-running-harness instead — it has rex Command hosting, ContextDB integration, and checkpoint recovery.
do-it-audit
Use when the user explicitly requests a deep repository or scoped audit; not for ordinary diff review.
do-it-skill-authoring
Use when creating or revising a do-it skill, its description, references, or specialist delegation guidance so it adds needed judgment without prescribing ceremony.
do-it-review
Use to assess requirements and implementation quality independently, or to resolve a batch of review findings.
do-it-architecture
Use when authority, ownership, contracts, dependency boundaries, migration, recovery, or structural deletion can change a design.
do-it-code-quality
Use when designing, changing, or debugging code to locate causal ownership and close the affected behavior.