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 2233admin/design-pipeline --skill corner-lasersgit clone --depth 1 https://github.com/2233admin/design-pipelineWrote 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/2233admin/design-pipeline/corner-lasers)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/corner-lasers"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/corner-lasers/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/2233admin/design-pipeline/corner-lasers"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/corner-lasers.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.00029 | $0.00560 |
| Opus 5 | $0.00015 | $0.00280 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
corner-lasers 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 8d 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.
This is a copy
100% identical to corner-lasers — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Corner Lasers Skill
Use When
- Create a corner-anchored laser composition with thin beams, a bright emitter node, bloom, and atmospheric glow or fog.
Workflow
Scope
- Apply this only to corner-based laser beam compositions, not to generic centered lasers, particle scenes, or unrelated motion systems.
- Use it when the design needs beams that originate from or converge at a corner or edge junction, with a strong cinematic emitter point.
Visual target
- Create two or three thin laser beams that meet at a bright corner emitter, then extend outward along different directions like a geometric room corner or portal seam.
- Keep the beam lines narrow and sharp with a white-hot center, a restrained halo, and strong bloom concentrated around the corner junction.
- Let the surrounding atmosphere glow softly from the emitter so the corner feels illuminated by volumetric haze rather than flat lines on a dark background.
- Use the design's primary color or strongest accent color for the halo and atmospheric tint instead of hardcoding blue, while keeping the brightest beam core near white.
Implementation guidance
- Prefer raw WebGL shader treatment or equivalent effect logic when the output supports it.
- Anchor the composition to an off-center corner point and derive multiple beam directions from that point rather than placing unrelated separate lines.
- Use signed-distance or line-distance logic so each beam stays thin, crisp, and continuous.
- Add a concentrated bloom or energy flare at the corner emitter where the beams meet; that hotspot should be the brightest point in the composition.
- Add subtle atmospheric glow, fog, or light diffusion around the beams so the effect feels immersive and spatial, not flat.
- Motion should stay restrained: slow pulsing, faint traveling energy, or gentle shimmer is good; chaotic flicker is not.
Tuning knobs
- Corner position: move the emitter point inward from the edge or corner to frame the composition.
- Beam count and angle: use two or three rays with clear directional contrast.
- Beam thickness: keep the core thin and tune the outer glow separately so the lasers stay elegant.
- Color: derive halo and haze tint from the active design accent color.
- Atmosphere: adjust bloom radius, fog density, falloff, and vignette strength so the corner stays luminous without washing out the UI.
What ships with it
8 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.
- demo/assets/page-01-2f563338-39fa-47ea-9761-658d4f3f84db-800w.jpg 72 KB
- demo/assets/page-02-fa51902b-c2a4-4c33-a96e-a8f1ef67edc6-800w.jpg 17 KB
- demo/assets/page-03-724142aa-44a6-48d3-9cf3-761e00d05b78-1600w.jpg 917 KB
- demo/assets/source-preview.jpg 73 KB
- demo/index.html 60 KB
- demo/preview.jpg 56 KB
- demo/PROMPT.md 3.3 KB
- demo/source.json 3.9 KB
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.
- 8d ago First seen · 43 lines · 29 tokens per session scan A 7a6766480ca8
corner-lasers is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 9d ago), licensed MIT. It adds 29 tokens to every session and 560 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to corner-lasers, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
extract-design
Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…
ss-lint
Quick automated lint — detects common design system violations in seconds.
ss-a11y
Audit a component or page for accessibility issues and fix them.
ss-copy
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone.
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…