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 egregore-labs/egregore --skill preview-designgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/preview-design)<a href="https://agentmods.dev/skills/egregore-labs/egregore/preview-design"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/preview-design/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/egregore-labs/egregore/preview-design"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/preview-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 10 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00071 | $0.00680 |
| Opus 5.5 | $0.00028 | $0.00272 |
| Sonnet 5.5 | $0.00014 | $0.00136 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
preview-design 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Topic: $ARGUMENTS
Preview the Design Convention
Renders a real Egregore artifact through this branch's MERIDIAN render path
(packages/egregore-artifacts local code) — deliberately not npx egregore-artifacts,
which pulls the published npm 0.10.2 (the OLD design). This is the test vector for
Design Convention Round 1: testers see the new design on real output before it merges.
Full protocol: memory/feedback/design-convention-r1/GUIDE.md.
When to invoke
User says: "/preview-design", "preview the design convention", "render with the new design", "let me test the new design on a document / handoff / board", or is running the design-convention round-1 test.
What it does
Run the bundled script — it handles dependency install and routes to the local CLI:
bash skills/preview-design/render.sh <surface> [file]
| Surface | Command | Input |
|---|---|---|
document |
render.sh document [file.md] |
any markdown — defaults to a bundled sample |
handoff |
render.sh handoff [file.json] |
a handoff-v1 JSON — defaults to a bundled sample |
platform |
render.sh platform |
reads memory/board/board.json (the board view) |
emissary |
render.sh emissary |
harness-only this round — prints the harness URL and stops |
The CLI opens the rendered HTML in the browser. After looking it over, the tester runs the
Socratic feedback protocol ("Run the Design Convention feedback protocol").
Why it's built this way
- Local, never
npx. It runsnode packages/egregore-artifacts/bin/cli.js, so you always get THIS branch's MERIDIAN design — npm'segregore-artifactsis the old look. - Lives in top-level
skills/, not.claude/skills/./updatereplaces.claude/skills/wholesale from upstream (git checkout upstream -- .claude/skills/), which would delete an org-local preview command. Top-levelskills/survives. - Emissary is excluded on purpose. Its renderer (
api/main.py) is server-side and not yet design-system-wired — wiring it is the #1 Round-2 task. For now it's reviewed via the published harness.
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 · 56 lines · 71 tokens per session scan A e64dea355678
preview-design is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 71 tokens to every session and 680 once invoked, about $0.0003 per session on Opus 5.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
get-context
Mandatory design-brief gate for clarifying the product and outcome. Use before ideation, image-to-code builds, redesigns, or product UI work to clarify missing product information and play back the brief before proceeding.
frontend
Builds, styles, and polishes anything drawn with HTML, CSS, or SVG: web UI, pages, components, HTML reports rendered to PDF or print, figures, PNG/SVG diagrams, slides, and images for Notion or Slack. Use for any styling, layout, animation, or visual-quality task, or when asked to make something look or feel a certain…
cli-anything-photoshop
A command-line tool that controls Adobe Photoshop through Windows automation. It can work with Photoshop documents, layers, selections, text, image adjustments, and exports.
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
app-screenshot-debug
Drive the running termio app via AppleScript / System Events to reach a UI state (focus the window, click a sidebar project, a terminal pane, a control), capture a pixel-accurate screenshot of just that window, and read it back for visual analysis — for diagnosing layout / spacing / alignment / 'this looks ugly'…
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…