
The MIT badge does not cover the style library
In short: Lemo-Opuscar's code is MIT, but its 99 style documents and prompts are CC BY-NC 4.0, so licence an agent skill artefact by artefact.
Outskill's 18 November 2026 video calls Lemomo's Lemo-Opuscar a free, MIT-licensed Claude Code plugin that turns a prompt into a short film. The repository is more careful. At commit f9e204293930, dated 20 November 2026, the code is MIT, while the Markdown guides, the style documents and the image-generation prompts are CC BY-NC 4.0 — non-commercial, with a limited permission for making films.
So the MIT badge does not cover the style library. That split matters the moment an agent skill goes into something a client pays for: the permissive licence sits on the engine, the restrictive one on the 99 styles you came for.
What the Outskill video actually shows
I watched the complete 59-second video and sampled playback at the opening, around 24, 40 and 47 seconds. It is a tidy demo: the agent writes a story, draws frames in code, composes music and voiceover, renders. The 59-style claim lands near 24 seconds, the repository and Claude Code workflow near 40, the hologram-bicycle example near 47.
It never says which artefacts that MIT grant covers. The description also points at a lemomab path; the project lives at lemomo-ai/lemo-opuscar. Fifty-nine seconds has to compress something; "free" and "MIT" are the wrong candidates.
Why the MIT badge does not cover the style library
The README at that commit is specific where the video is loose. The current release contains 99 styles, not 59. One film takes an agent roughly 30 to 60 minutes and a fair amount of tokens. It needs Node 20+, ffmpeg 7+ and Python 3.11+ or uv.
The licence is four grants rather than one. Code is MIT. Markdown guides, style documents and image-generation prompts are CC BY-NC 4.0, with a limited permission to produce films and deliver project files. Demo films, stills and subtitles are CC BY 4.0, subject to listed exclusions and third-party rights. Films you make are yours, subject to third-party inputs.
Read it as an engineer: the permissive grant covers the code, while the non-commercial terms cover the 99 style documents and the prompts driving them. That is the asset.
The five rows I fill in before approving a skill
This is my editorial judgment, not a Trigent finding, a client result or legal advice. When a badge and a licence file disagree, I stop reading the badge and fill in five rows.
| Artefact | What it is here | Terms at commit f9e204293930 |
|---|---|---|
| Code | plugin, scripts, renderer | MIT |
| Instructions and prompts | guides, 99 style documents, image prompts | CC BY-NC 4.0 plus a limited film permission |
| Demo assets | sample films, stills, subtitles | CC BY 4.0, with exclusions and third-party rights |
| Generated outputs | the films you render | yours, subject to third-party inputs |
| Third-party inputs | models, voices, fonts a run touches | not answered by this repository |
The repository answers four rows. The fifth is yours to chase.
I have not installed or run Lemo-Opuscar, so I cannot vouch for output quality, the 30-to-60-minute range or the token bill, and I am not ruling on whether a given commercial use infringes anything. I checked which document governs which artefact on 21 November 2026; a licence pinned to a commit can move on the next push.
What's in it for you
- Put those five rows in your intake checklist for any plugin or skill pack you ship in paid work.
- Pin the commit you read. An "MIT" line on a September README is not what you inherit in November.
- Treat demo media and generated output as separate questions from the code; the exclusions live there.
Licence an agent skill artefact by artefact: the badge covers the engine, not the style library that makes it worth running.


