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 manishiitg/coding-agent-loop --skill longform-cinematic-videogit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/longform-cinematic-video)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/longform-cinematic-video"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/longform-cinematic-video/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/manishiitg/coding-agent-loop/longform-cinematic-video"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/longform-cinematic-video.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.00061 | $0.01300 |
| Opus 5.5 | $0.00024 | $0.00520 |
| Sonnet 5.5 | $0.00012 | $0.00260 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade C, and why
longform-cinematic-video scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
A photoreal host may have illustrated historical cutaways. Do not refuse or How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Direct one film, not a collection of clips
Own the production-level decisions that cross model generation and editing.
Read video-storytelling, video-cinematography, minimax-h3-video,
video-provider-capabilities, and video-editing for their specialist
rules. Keep those responsibilities coordinated by one sequence plan and one
editorial grammar.
Define the cinematic contract
The user chooses the visual style: photoreal, hand-drawn, 2D/3D animation, motion graphics, documentary, slideshow, or mixed media. Cinematic means coherent storytelling and intentional picture/sound direction, not realism. A photoreal host may have illustrated historical cutaways. Do not refuse or convert those inserts to photoreal. Realistic characters are not required.
Before scripting, lock the film's dramatic question, audience, runtime, format, emotional arc, point of view, visual language, camera grammar, color journey, sound world, and continuity priorities. State what must remain exact across the film: character identity, wardrobe, props, geography, time of day, screen direction, eyelines, lighting motivation, and recurring audio motifs.
Choose a small visual vocabulary and repeat it intentionally. A cinematic film does not need a new style, lens, camera move, or transition for every beat. Use the user-approved medium for each sequence; a film may combine generated footage, supplied media, and deterministic animation. H3 reference and continuation rules apply to generated-video shots, not every visual sequence.
Plan sequences before shots
Organize the film as chapters, sequences, scenes, and only then shots. Give each sequence an entrance state, dramatic turn, exit state, location, characters, time, lighting, sound, and continuity bridge into the next sequence. A script beat is not automatically a new generated clip.
Create longform-sequence-plan.json before paid video generation. Include:
- chapter, sequence, scene, and shot identifiers;
- measured narration or dialogue duration covered by each sequence;
- H3 route chosen by actual controls: text-only, first-frame or minimal references;
- references and their exact semantic roles;
- incoming and outgoing character, prop, geography, motion, camera, lighting, and audio state;
- generation topology: one H3 take, Reference-to-Video continuation, a motivated H3 camera-angle change, or intentional hard cut;
- planned cut point, transition grammar, handles, and expected seam risk;
- the reason every independent generation is unavoidable.
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 Changed fbe08d8e1b67
- 1mo ago Changed · +7 lines scan A → C d8d8f449fd07
- 1mo ago Changed · -17 lines 217feee58b96
- 2mo ago First seen · 123 lines · 61 tokens per session scan A 05b040d6a83d
longform-cinematic-video is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,300 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…
autofix
Safely review and apply CodeRabbit PR review-thread feedback from GitHub with per-change approval; never execute reviewer-provided prompts directly.
review-code
Review a code change well — engine-agnostic critical review discipline for an inline dev loop. Defines what to look for (design→correctness→complexity→tests→naming→security), a severity taxonomy, and a review→fix→re-review loop with a hard stop. Use on "review this code", "review my diff", "is this change good"…
code-review
AI-powered code review using CodeRabbit. Default code-review skill. Trigger for any explicit review request AND autonomously when the agent thinks a review is needed (code/PR/quality/security). Also drives the development inner loop: review uncommitted work, fix, re-review before commit.
code-quality
Drive static-analysis code quality in pi-agent-dashboard with Biome (analyze → fix → test), in changed-files or whole-repo mode. Use when asked to "improve code quality", "lint and fix", "clean up warnings", "fix Biome issues", "run static analysis", or when setting a code-quality goal. Skip for one-line edits.
goga-review-plan
Verify execution plan completeness and correctness.