Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md one this `SKILL.md` sits in. From anywhere else nothing resolves — use the
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Ofox video-generation workflow that uses user-provided images and an API key with an explicit cost-approval step before paid jobs.
Before installing, confirm you trust the Ofox publisher and are comfortable sending the selected images to Ofox for generation. Prefer a reviewed or pinned installer path for ofox-video-core when possible, keep OFOX_API_KEY scoped to Ofox use, and only approve paid runs after reviewing the dry-run cost table.
Referenced artifact was not completely inspected
one this `SKILL.md` sits in. From anywhere else nothing resolves — use the
Referenced artifact was not completely inspected
one this `SKILL.md` sits in. From anywhere else nothing resolves — use the
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.
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.
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.
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.
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.
This line recommends 'npx ofox-skills' as the way to install every skill in the repo so sibling paths resolve. Even in changelog prose, normalizing an unpinned broad installer increases supply-chain risk and can lead a user or agent to fetch and execute whatever package version is current at runtime, with a wider-than-necessary installation scope.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
---
name: keyframe-animation
description: Requires OFOX_API_KEY — create one at https://app.ofox.ai, plus two images you already have, a start frame and an end frame. Animates the motion between them as one video — both frames go into a single Ofox video job, the clip opens on A, closes on B, and the model fills the middle. Use when a user has two stills and wants the in-between animated, e.g. "here is the before and the after, animate the transition", "make a video that starts on this image and ends on that one", "tween these two frames", or "move the object from where it sits in the first picture to where it sits in the second". Do not use when only one image exists (animating a single frame is seedance-ad-creative or seedance-product-video), or when the pair is two states of a user interface (see product-demo).
license: MIT
version: "2.0.0"
homepage: https://github.com/ofoxai/skills/tree/main/skills/keyframe-animation
The skill instructs users to install a dependency via npx skills add ... without pinning a version, which exposes them to supply-chain drift or a compromised latest release. Because this is an installation command that users are explicitly told to run when a prerequisite is missing, the documentation materially increases the chance of executing unreviewed code from the registry.
This line recommends npx ofox-skills ofox-video-core without a fixed version, so anyone following the instructions will execute whichever package version is current at the time. If the package or one of its transitive dependencies is compromised, that can lead to arbitrary code execution on the user's machine during installation or startup.
The changelog states that installing every skill in the repo is what keeps sibling paths resolvable, which effectively endorses an overbroad installation path without presenting a narrower default. That can push users or downstream agents toward unnecessary code installation outside the immediate need, increasing attack surface and the blast radius of any compromised package or skill.