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 SummerEngine/summer-engine-agent --skill lightninggit clone --depth 1 https://github.com/SummerEngine/summer-engine-agentWrote 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/summerengine/summer-engine-agent/lightning)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/lightning"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/lightning.svg" alt="Measured on agentmods" 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.00065 | $0.05227 |
| Opus 5 | $0.00032 | $0.02613 |
| Sonnet 5 | $0.00013 | $0.01045 |
| Haiku 4.5 | $0.00006 | $0.00523 |
Grade A, and why
lightning 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 3d 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lightning — Procedural Jagged Bolt
A lightning bolt is a noisy line from A to B, drawn for ~150 ms with a glow shader, sparks at both endpoints, and camera shake on cast. The recipe builds the jagged path in GDScript (midpoint displacement on a polyline), feeds the verts into an ImmediateMesh, applies a ShaderMaterial for additive bloom + flicker, spawns hit-spark particles at each endpoint, and calls CameraShake.add_trauma(0.6) for the impact. Used for shock spells, tesla coils, weapon discharges, electric enemies.
When to use
- "Cast a lightning bolt from the wizard's hand to the enemy."
- "Chain lightning from one enemy to the next." (call
cast_lightningper segment) - "Tesla coil firing at the player every 2 seconds."
- "Energy weapon laser." (use the
laser-beamvariant) - "Lightning strike from the sky."
- The user wants a short, dramatic energy connection between two points.
When NOT to use
- The user wants a continuous beam that holds (e.g., laser sniper holding the trigger) — use the same shader on a
MeshInstance3Dcylinder with continuous emission, not theImmediateMeshone-shot pattern. (See variants forheld-beam.) - The user wants ambient electricity on an object (Frankenstein arcs) — use a custom shader on the mesh with screen-space arcs; this recipe is for two-point bolts.
- The user wants a 2D lightning effect on UI —
canvas_itemshader, not this. - The user wants a tracer line for a bullet — use a simple
ImmediateMeshwithout noise displacement; skip this recipe. The current Summer build has noLine3D(ClassDB.class_exists("Line3D")isfalse);Line2Dis 2D-only.
Recipe
1. Files to create
addons/vfx/lightning/lightning.gdshader # spatial shader for the bolt mesh
addons/vfx/lightning/lightning_caster.gd # build path, draw, animate, spawn endpoints, shake
addons/vfx/lightning/lightning.tscn # reusable scene
2. Shader code
addons/vfx/lightning/lightning.gdshader:
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.
- 3d ago First seen · 405 lines · 65 tokens per session scan A 4a75ccad11c9
lightning is a skill published in the GitHub repository SummerEngine/summer-engine-agent (57 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 5,227 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
self-evolve
Capture reusable patterns from a finished project and lift them into framework-level priors (contracts, modules, skeletons) that future projects inherit. Run only when the user explicitly requests self-evolution; the orchestrator executes the workflow.
artist-self-evolve
Distill stable art-generation patterns from a completed project, so future projects produce comparable assets without re-discovering the prompts. Lead-dispatched only — orchestrator invokes this skill from its self-evolve flow with a game-slug message; do not self-trigger.
vibegame-build
Run VibeGame's standard end-to-end game development workflow with reviewer gates. Use when the user wants to create a game from zero or evolve an existing game across multiple stages.
vibegame-start
Resume a VibeGame orchestrator session after vibegame start. Use at the beginning of a Claude or Codex session to inspect team runtime state, repair missing persistent members, load goal and GDD context, inspect tasks, and ask the user what to do next.
vibegame-edit
Iterate broadly on an existing game, on top of vibegame-build. Use when the user asks to change an existing game's art style, genre, or core rules. Not for local tuning such as numbers or game feel. Orchestrator only.
hearth-feel
Make a Hearth game feel good, not just run — the juice stack (hit-stop, screen shake, flash, particle bursts, layered sound), tween easing, camera effects, anticipation/recovery animation idioms, game-UX conventions (menus, pause, onboarding, difficulty, save etiquette), effect-asserting playtests, and the quality bar…