Borrowing it
Nothing to install: this file belongs to kwakseongjae/oh-my-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kwakseongjae/oh-my-design/main/.agents/skills/omd-add-reference/SKILL.mdgit clone --depth 1 https://github.com/kwakseongjae/oh-my-designWrote 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/kwakseongjae/oh-my-design/omd-add-reference)<a href="https://agentmods.dev/skills/kwakseongjae/oh-my-design/omd-add-reference"><img src="https://agentmods.dev/badge/skills/kwakseongjae/oh-my-design/omd-add-reference/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/kwakseongjae/oh-my-design/omd-add-reference"><img src="https://agentmods.dev/badge/skills/kwakseongjae/oh-my-design/omd-add-reference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.00368 |
| Opus 5 | $0.00020 | $0.00184 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
omd:add-reference 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 11d 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.
What it actually says
omd:add-reference — Core v2 catalog cutover gate
Status: CORE_V2_CATALOG_WRITE_BLOCKED.
This repository still reads the 440 historical reference files through the
legacy frontmatter adapter. That makes them valid migration inputs, but it does
not authorize a new legacy writer. Do not create, update, backfill, or sync a
web/references/<id>/DESIGN.md from this skill.
When invoked:
- Inspect only. Do not write a reference, token block, generated catalog, or public count.
- Explain that project/user-facing DESIGN.md is already single-write Core v2, while reference authoring is paused until the catalog has a graph-backed metadata/evidence package and Core projection compiler.
- If research is still useful, save nothing to the catalog. Return a concise proposed source list and the intended reference id in chat only.
- Resume writes only after all of these exist and pass together:
- Core v2 reference metadata/evidence sidecar schema;
- registry, quality, AST, token, and verification readers for that schema;
- deterministic graph → portable DESIGN.md projection;
- legacy dual-read and Core single-write tests;
- migration report with
dropped_segments=0and unknown facts absent.
Never work around this gate by restoring a legacy YAML marker, numbered 13/15/16 sections, placeholder sentinels, or a second authoritative Markdown dialect.
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.
- 11d ago First seen · 35 lines · 41 tokens per session scan A 61347b6b12b7
omd:add-reference is a skill published in the GitHub repository kwakseongjae/oh-my-design (498 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 368 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
dembrandt
A TypeScript command-line tool that renders a web page with Playwright and examines its actual styles. It turns colours, typography, spacing, borders, shadows, animation curves, components, and breakpoints into structured design tokens.
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…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
intake
The guided walkthrough for a codebase that has just installed montology (or has never written its vocabulary down) — phased questions served to the people who own the code as a clean one-question-at-a-time form in their browser (a local HTML file, no hosted service), answers returned to the agent on disk, each round…
brandmd
Extract a website's design system into a DESIGN.md file. Use when starting a new frontend project, rebuilding a site, or when the user wants AI-generated UI to match an existing brand.
montology
A repo's vocabulary as a database, enforced against the code by a tree-sitter scan — in every language it declares (Python, TypeScript/JS, Go, Rust, Swift, Java, Ruby, Elixir, C/C++, and more). Use BEFORE naming anything in code — a class, struct, function, type, module, table, column, endpoint, event, env var, CLI…