Borrowing it
Nothing to install: this file belongs to alfredoperez/speckit-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alfredoperez/speckit-companion/main/.claude/skills/feature-clip/SKILL.mdgit clone --depth 1 https://github.com/alfredoperez/speckit-companionWrote 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/alfredoperez/speckit-companion/feature-clip)<a href="https://agentmods.dev/skills/alfredoperez/speckit-companion/feature-clip"><img src="https://agentmods.dev/badge/skills/alfredoperez/speckit-companion/feature-clip/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/alfredoperez/speckit-companion/feature-clip"><img src="https://agentmods.dev/badge/skills/alfredoperez/speckit-companion/feature-clip.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 6 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00049 | $0.02005 |
| Opus 5 | $0.00024 | $0.01002 |
| Sonnet 5 | $0.00010 | $0.00401 |
| Haiku 4.5 | $0.00005 | $0.00200 |
Grade A, and why
feature-clip 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature clip
The landing page and the docs are carried by short looping clips: a product screenshot,
a camera that moves across it, a ring around the region being named, and a caption band.
This skill owns how this repo makes them. The composition contract itself — GSAP
timelines, the HyperFrames runtime, keyframes, the CLI — belongs to the upstream
hyperframes-* skills. Defer to those for anything about the engine, and use this for
anything about the pipeline.
The chain
capture → compose → storyboard → render → web encode → sync → check
Every stage has a command. None of them takes an argument you have to remember.
npm run clips:new -- <id> "Human name" # scaffold from _template
npm run clips:capture -- --clips <id> # shoot the source PNGs from Storybook
(cd media/feature-clips/<id> && npm run render) # composition -> canonical MP4
npm run clips:render -- <id> # -> media/web: webm, mp4, poster, 16:9 card
npm run clips:stills # hero and accordion crops -> media/web
npm run clips:gifs -- <id> # -> docs/screenshots/generated/<id>.gif
npm run clips:sync # -> website/public/media
npm run clips:check # storyboard drift + manifest
npm run clips:outline -- <id> # pacing: t, hold and label per beat
npm run clips:scenes -- <id> # scene and step list, for review
clips:capture with no --clips shoots the documentation images instead: the
STORIES list, which feeds docs/screenshots/generated/. Both lists live in
scripts/capture-docs-images.mjs.
npm run clips:render -- --list prints which render file each id resolves to. Run it
before any full encode. It is how you catch a stale source before it ships.
Starting a new clip
npm run clips:new copies media/feature-clips/_template, substitutes the id, adds a
CLIP_CAPTURES stub, and registers the feature in media/manifest.json. Do not copy a
neighbouring composition by hand: the template is where the current caption, scrim and
pacing rules live, and a hand copy inherits whichever clip happened to be nearest.
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.
- 12d ago First seen · 149 lines · 49 tokens per session scan A 07ff0f20cfbd
feature-clip is a skill published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 2,005 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-08-30.
Other skills, from other repositories
deno-knowledge-patch
Use this skill when choosing current Deno runtime APIs, CLI options, configuration, dependency behavior, Node compatibility, or deployment workflows. Open the topic reference before changing a project because several commands, flags, APIs, and defaults changed more than once.
bun-knowledge-patch
Use this skill when working on Bun applications, packages, builds, tests, servers, or Node.js compatibility. Check the relevant reference before relying on older Bun behavior or translating Node-oriented code.
drizzle-knowledge-patch
Use this skill when work touches Drizzle SQL identifiers or aliases, Drizzle Kit module loading, or Zod schemas generated from Drizzle tables.
ts-debug
TypeScript/Node debugging expert. Use when the user needs to debug, profile, or trace TypeScript or Node.js code — e.g. "how do I debug this", "find the memory leak", "why is this slow", "add a breakpoint", "profile this function", "why won't the process exit".
typescript-pro
Implements advanced TypeScript type systems, creates custom type guards, utility types, and branded types, and configures tRPC for end-to-end type safety. Use when building TypeScript applications requiring advanced generics, conditional or mapped types, discriminated unions, monorepo setup, or full-stack type safety…
api-development
This skill should be used when implementing backend API services, file operations, and process management in TypeScript/Node.js.