web-technique-to-skill

web-technique-to-skill is a skill for Codex from 2233admin/design-pipeline. It costs 148 tokens per session (3,611 once invoked), scanned A, a copy of web-technique-to-skill, MIT.

A workflow for turning a working visual or interaction technique into a reusable web-design skill with a focused mechanism and a demo. It starts from code that already works and preserves the approved surrounding design.

In plain words
What is it for?
Use it to package effects such as custom motion, scrolling behavior, or visual transitions into documented skills and demos that prove the behavior and its visual accuracy.
Why use it?
It prevents useful implementation knowledge from remaining trapped in one page or file and keeps each reusable skill focused on one clear effect.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to package effects such as custom motion, scrolling behavior, or visual transitions into documented skills and demos that prove the behavior and its visual accuracy.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/2233admin/design-pipeline/web-technique-to-skill
Install

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.

Any agent
npx skills add 2233admin/design-pipeline --skill web-technique-to-skill
Clone the repo
git clone --depth 1 https://github.com/2233admin/design-pipeline

Made for: Codex.

Wrote 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.

agentmods badge for web-technique-to-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/2233admin/design-pipeline/web-technique-to-skill/github.svg)](https://agentmods.dev/skills/2233admin/design-pipeline/web-technique-to-skill)
Your own site
<a href="https://agentmods.dev/skills/2233admin/design-pipeline/web-technique-to-skill"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/web-technique-to-skill/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.

agentmods 80×15 button for web-technique-to-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/2233admin/design-pipeline/web-technique-to-skill"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/web-technique-to-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 148 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,611 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00148 $0.03611
Opus 5 $0.00074 $0.01806
Sonnet 5 $0.00030 $0.00722
Haiku 4.5 $0.00015 $0.00361

Measured 6d ago against content hash 8868b6b6940e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

web-technique-to-skill 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 6d 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.

Origin

This is a copy

100% identical to web-technique-to-skill — 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.

skill/references/mengto-skills/upstream/agent-skills/codex/web-technique-to-skill/SKILL.md · 206 lines

How it starts

The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Web Technique to Skill

Start from working code, not from prose. Reach for article-prompts-to-skills when the source is an article or a prompt pack that describes behavior. Reach for this when you built the thing, it works, and the knowledge is currently trapped in one file.

Extract one mechanism per skill. A page that turned out well usually holds several; package them separately or each one gets diluted.

Treat this as the living quality contract for every web-technique skill. On every creation or revision, audit this skill too. If the work exposes a missing fidelity rule, failure mode, packaging constraint, or verification step, update this contract in the same scoped change instead of solving it only inside one child skill.

Name the mechanism in one sentence

Write the sentence before you write anything else: the one thing that, if removed, makes the effect stop working. If you cannot write it, you have a look, not a mechanism, and there is no skill here yet.

The sentence decides everything downstream. For a leaf fall it is "the tumble crosses edge-on, and that instant of near-disappearance is what the eye reads as a leaf" — so the sprite artwork, the palette, and the night scene are all staging, and the tumble is the skill.

Test it: change the subject, the palette, and the layout in your head. If the sentence still holds, it is the mechanism. If it stops making sense, you named the staging.

Name the demo and disclose the stack

Use the concrete technique name for the visible h1 and browser <title>: Wisps, Cursor Ripples, Liquid Metal Border, or Scroll-scrubbed Word Reveal. Do not hide the subject behind an abstract mechanism claim. “Draw at any speed” describes behaviour, but it does not tell anyone what the demo is.

Put the verified implementation path directly above or below that title. Name, in order:

  1. The runtime or framework: Vanilla JavaScript, React, Vue
  2. The renderer or browser API: Canvas 2D, WebGL, DOM/CSS, SVG
  3. The technique layer when present: GLSL shaders, Three.js, GSAP, ScrollTrigger

Read the full file on GitHub · 206 lines

Files

What ships with it

6 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.

Changes

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.

  1. 6d ago First seen · 206 lines · 148 tokens per session scan A 8868b6b6940e

Subscribe to this mod's changes

web-technique-to-skill is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 7d ago), licensed MIT. It adds 148 tokens to every session and 3,611 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to web-technique-to-skill, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

designlang-tokens

Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

Manavarya09/design-extract · 30 tokens

s2-docs

Look up Spectrum 2 (S2) component documentation, design guidelines, and usage patterns when building with React Spectrum or Spectrum Web Components. Use when the user mentions Spectrum, S2, React Spectrum, RSP, Spectrum Web Components, or SWC, or names a Spectrum component (Button, Picker, ComboBox, TextField…

adobe/spectrum-design-data · 91 tokens

use-design-md

Pull a Korean brand's published design.md from the ko-design-md catalog (getdesign.kr) and apply its design language — colors, typography, spacing, radius, components, do's & don'ts — to the UI you are building in the CURRENT project. Use this skill whenever the user wants to build or restyle UI in the style of a…

CaesiumY/ko-design-md · 226 tokens

design-to-code-check

Check alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison. Trigger when someone says: does this match the design, check implementation, design code alignment, what's different between the design and the build, spec check…

murphytrueman/design-system-ops · 95 tokens

design-engineering

Premium design engineering skill for agentic workflows — produces high-end, distinctive UI designs using DESIGN.md as the portable contract across Pencil MCP (in-IDE canvas), Figma MCP (team handoff + design tokens), and Google Stitch (vibe exploration + AI generation). Enforces anti-generic principles, WCAG 2.2 AA…

broomva/skills · 231 tokens

fmcp-token-sync-orchestrator

Figma design token'larını kod dosyalarıyla (CSS/Tailwind/Swift/Compose) platform-agnostic senkronize eder. Diff preview + onay + write akışı zorunlu. Her platformda çalışır. Condensed-first: Essentials bölümü %80 case'i kapsar, Advanced sadece edge case'lerde.

atezer/FMCP · 79 tokens