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 ezesubu/VERA --skill scene-vibegit clone --depth 1 https://github.com/ezesubu/VERAWrote 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/ezesubu/vera/scene-vibe)<a href="https://agentmods.dev/skills/ezesubu/vera/scene-vibe"><img src="https://agentmods.dev/badge/skills/ezesubu/vera/scene-vibe/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/ezesubu/vera/scene-vibe"><img src="https://agentmods.dev/badge/skills/ezesubu/vera/scene-vibe.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.00000 | $0.00553 |
| Opus 5.5 | $0.00000 | $0.00221 |
| Sonnet 5.5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
scene-vibe 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 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.
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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scene Vibe
VERA can set the cinematic mood of the level currently open in the Unreal editor in a single command — perfect right before taking a showcase screenshot or recording a demo of a game. Pick a mood, capture the beauty shot, then restore the level.
Tools
set_vibe (destructive, reversible)
Apply a cinematic mood to the open level. Argument:
mood— one of the 5 moods below.
It spawns (or reuses, if already present) a tagged DirectionalLight and a tagged, unbound PostProcessVolume, then applies curated color grading (saturation, contrast, gain, split-tone shadows/highlights), exposure bias, bloom, vignette and — where the build supports it — film grain, plus a matching sun color, intensity and angle. It is idempotent: calling it again (even with a different mood) reuses the same two actors instead of stacking new ones.
clear_vibe (destructive, reversible)
Remove the vibe. Destroys every actor tagged VERA_Vibe (the DirectionalLight and the
PostProcessVolume that set_vibe added) and leaves everything you authored untouched,
restoring the level's original look. Safe to call even when no vibe is active.
The 5 moods
- cyberpunk — cool teal/blue shadows with magenta highlights, high contrast, bloom turned up, a slight vignette; dim cool directional light.
- horror — very dark and desaturated, cold tint, heavy vignette, low exposure; weak reddish directional light.
- golden_hour — warm orange sun low on the horizon, soft and gentle bloom, warm tint.
- noir — near-monochrome (very low saturation), high contrast, strong vignette; hard white key light.
- aztec_dusk — warm amber and purple split-tone, atmospheric, medium exposure; orange sun low on the horizon.
How VERA uses it
- Call
set_vibewith the mood that fits the shot (e.g.cyberpunkfor a neon city). - Take the showcase screenshot or start the recording.
- Call
clear_vibeto restore the level when done.
Fully reversible — the vibe is just two tagged actors, and clear_vibe removes them.
Every editor operation is individually guarded, so an unavailable property degrades
gracefully and the rest of the look still applies; the tools never crash the editor.
What ships with it
3 files 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 First seen · 47 lines · 0 tokens per session scan A 84ba941a1976
scene-vibe is a skill published in the GitHub repository ezesubu/VERA (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 553 tokens. 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
game-development
Game development orchestrator. Routes to platform-specific skills based on project needs.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
game-art
Game art principles. Visual style selection, asset pipeline, animation workflow.
game-audio
Game audio principles. Sound design, music integration, adaptive audio systems.
multiplayer
Multiplayer game development principles. Architecture, networking, synchronization.
pc-games
PC and console game development principles. Engine selection, platform features, optimization strategies.