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 OpenLAIR/OpenSkill --skill evo-video-filler-word-removergit clone --depth 1 https://github.com/OpenLAIR/OpenSkillWrote 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/openlair/openskill/evo-video-filler-word-remover)<a href="https://agentmods.dev/skills/openlair/openskill/evo-video-filler-word-remover"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-video-filler-word-remover/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/openlair/openskill/evo-video-filler-word-remover"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-video-filler-word-remover.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.00045 | $0.01051 |
| Opus 5 | $0.00023 | $0.00526 |
| Sonnet 5 | $0.00009 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
evo-video-filler-word-remover 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evo-video-filler-word-remover
Purpose
Detects filler words and phrases in interview videos using speech recognition (faster-whisper), outputs timestamped annotations as JSON, and stitches all filler word clips into a single compilation video.
Key Concepts
- Uses faster-whisper (CTranslate2-based Whisper) for CPU-optimized transcription
smallmodel withint8quantization: optimal tradeoff between accuracy and CPU speed (~1GB RAM, 1.5-3x real-time)- Word-level timestamps via DTW cross-attention alignment (~20ms resolution)
- VAD filter (Silero) enabled to prevent hallucination on silence
condition_on_previous_text=Falseto prevent the model from skipping disfluencies in favor of grammatically clean output- Dual-pass detection: multi-word phrases first (greedy longest match), then single-word fillers
- Text normalization: lowercase, strip punctuation, handle Whisper's leading-space tokenization artifacts
- Hesitation equivalence: um, uh, hum, hmm, mhm, umm variants all recognized
- Frame-accurate cutting with re-encoding (libx264/aac) — stream copy cannot achieve sub-second precision due to keyframe spacing
- MPEG-TS intermediate containers for seamless concat demuxer stitching
- Timestamp padding (150ms before, 100ms after) to capture full acoustic envelope of filler utterances
- Overlapping segment merging (gap < 100ms threshold) to avoid micro-cuts
Filler Words Detected
Single-word
um, uh, hum, hmm, mhm, like, yeah, so, well, okay, basically
Multi-word (n-gram scan)
you know, i mean, kind of, i guess
Usage
import sys
sys.path.insert(0, '/app/environment/skills/evo-video-filler-word-remover/scripts')
from utils import run_pipeline
# Full pipeline
fillers = run_pipeline('/root/input.mp4', '/root/annotations.json', '/root/output.mp4')
# Or step by step:
from utils import (extract_audio, transcribe_audio, detect_fillers,
compute_segments, extract_and_stitch)
audio_path = extract_audio('/root/input.mp4')
words = transcribe_audio(audio_path, model_size='small')
fillers = detect_fillers(words)
segments = compute_segments(fillers)
extract_and_stitch('/root/input.mp4', segments, '/root/output.mp4')
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.
- yesterday First seen · 78 lines · 45 tokens per session scan A a1f1e3900d0b
evo-video-filler-word-remover is a skill published in the GitHub repository OpenLAIR/OpenSkill (90 stars, last pushed 2d ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,051 once invoked, about $0.0002 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-11.
Other skills, from other repositories
flux-analyzer
Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.
experimental-design
Best practices for designing reproducible ML experiments. Use when planning ablations, baselines, or controlled experiments.
prolong
Recover and use durable coding-session history from PRO-LONG's local append-only log. Use on long-running coding tasks, after context compaction or session resume, when reconstructing prior decisions or tool results, or before repeating work that may already have been attempted.
resolving-merge-conflicts
Use when a git merge or rebase reports conflicts and the operation is in progress.
security-review
Use when reviewing code for vulnerabilities, checking diffs for injection/XSS/auth/crypto issues. Invokes on code changes (.go/.py/.js/.ts/.java/.rs/.php/.rb), not docs-only diffs.
script-exec-blocked
Sandbox approval policy blocks executecode and python3 -c; use readfile/writefile + manual transforms instead of retrying both runners.