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 DKeken/codex-skills-alternative --skill design-sharegit clone --depth 1 https://github.com/DKeken/codex-skills-alternativeWrote 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/dkeken/codex-skills-alternative/design-share)<a href="https://agentmods.dev/skills/dkeken/codex-skills-alternative/design-share"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-share/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/dkeken/codex-skills-alternative/design-share"><img src="https://agentmods.dev/badge/skills/dkeken/codex-skills-alternative/design-share.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.00092 | $0.00898 |
| Opus 5.5 | $0.00037 | $0.00359 |
| Sonnet 5.5 | $0.00018 | $0.00180 |
| Haiku 4.5 | $0.00009 | $0.00090 |
Grade A, and why
design-share 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design — Share
Get the prototype in front of reviewers with a working link + clear run notes. Final handoff stage. The goal is that someone who wasn't involved can open it, know what to look at, and leave useful feedback — without you in the room.
When to use
- A QA'd prototype is ready to circulate for feedback.
- "Share it", "give me a link", "publish", "let the team see it".
- Handing off to stakeholders for review/sign-off.
When NOT to use
- The prototype hasn't passed
design-qa(especially HIGH items) — fix or explicitly flag first. - It's not runnable yet →
design-prototype.
Inputs
- The QA'd prototype (path).
- Share method: local serve, tunnel, or deploy to a host.
- Host/account constraints — ask before deploying anywhere external.
Workflow
- Confirm it runs clean: install + build + start. Fix any breakers before sharing.
- Pick the share method:
- Local — serve on a port; give the localhost URL + start command (good for solo/local review).
- Tunnel — expose local via a tunnel; only if the user wants external access right now.
- Deploy — push to a preview host (Vercel/Netlify/etc.). Only with explicit user go-ahead, since it sends code off-machine.
- Write a review note: what to look at, the happy path to click, known stubs/TODOs, where to leave feedback.
- Return the link + run instructions + review note.
Worked example
method: local serve (user wants to review on their machine)
preflight: `npm install` ok, `npm run build` clean, `npm run dev` boots :5173 ✓
deliverable:
link: http://localhost:5173
run: `npm install && npm run dev`
review this: complete the onboarding happy path (Welcome → Template → Name → Dashboard);
check the empty-name error and the loading state on "Create"
known stubs: templates are 3 fixtures; "Create" writes to in-memory store (no real API yet)
feedback: leave notes in #design-review or as comments on the Figma frame
(If deploy was requested: confirm host, check for secrets/env files, deploy, return the live URL + same review note.)
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 · 65 lines · 92 tokens per session scan A 8a70ec0039f7
design-share is a skill published in the GitHub repository DKeken/codex-skills-alternative (15 stars, last pushed 4mo ago), licensed MIT. It adds 92 tokens to every session and 898 once invoked, about $0.0004 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
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
website-to-video
Capture a general website/URL and turn it into a HyperFrames video (site tour, showcase, or social clip from the site's own visuals). Uses headless Chrome screenshots + brand assets. Use when intent is general — portfolio/blog/landing-page showcase or social clip from the site. NOT for: product/SaaS launch or promo (→…
qa/e2e-playwright
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website"…
browser
Drives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA…