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 agentmods add skills/pymodel/designer-skill/releasenpx skills add PyModel/designer-skill --skill releasegit clone --depth 1 https://github.com/PyModel/designer-skillWhat 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 | $0.00050 | $0.01225 |
| Opus 5 | $0.00025 | $0.00613 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
release 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 2d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release
Ship designer-skill-mcp in one ordered sequence: version bump → build/test → commit → tag → push → npm → GitHub release.
Default version bump
Every release bumps the minor version by 0.1.0 and resets patch to 0, unless you pass an explicit semver to the script.
| Current | Next (default) |
|---|---|
0.10.0 |
0.11.0 |
0.11.0 |
0.12.0 |
0.9.1 |
0.10.0 |
Rule: {major}.{minor + 1}.0 — never auto-bump patch. Use an explicit version only for hotfixes (e.g. ./scripts/release.sh 0.11.1 "hotfix").
Preflight
- Commit and push all feature work first. The release script only commits version bump files.
- Working tree must be clean except intentional release edits.
npm whoamimust succeed (logged in as a publisher for@pymodel/designer-skill-mcp).gh auth statusmust succeed (active account:elkaix— branch protection onmain).- After release, update doc pins in
README.mdandcommands/designer-setup.md(@latest→@<new-version>).
Version touchpoints (keep in sync)
| File | Field |
|---|---|
designer-skill-mcp/package.json |
"version" |
designer-skill-mcp/package-lock.json |
top-level "version" |
designer-skill-mcp/server.json |
"version" + packages[0].version |
.claude-plugin/plugin.json |
"version" |
.codex-plugin/plugin.json |
"version" |
.cursor-plugin/plugin.json |
"version" |
README.md |
pin example (@0.11.0) |
commands/designer-setup.md |
pin example (@0.11.0) |
Tag format: v{semver} (e.g. v0.11.0).
Automated (preferred)
From repo root:
chmod +x scripts/release.sh
# Default: auto-bump minor (+0.1.0), e.g. 0.10.0 → 0.11.0
./scripts/release.sh "Short release notes for GitHub and the tag body."
# Override only when you need a patch or major bump
./scripts/release.sh 0.11.1 "Hotfix: …"
./scripts/release.sh 1.0.0 "Breaking: …"
The script runs this sequence:
- Resolve version (auto minor bump, or use explicit semver)
npm version <semver> --no-git-tag-versionindesigner-skill-mcp/- Sync plugin manifests +
server.json npm run build+npm test- Commit version files with a release message
- Annotated tag
v<semver> git push origin HEAD+git push origin v<semver>npm publish --access publicfromdesigner-skill-mcp/mcp-publisher publishfromdesigner-skill-mcp/(if installed and logged in)gh release create v<semver>- Update
README.mdandcommands/designer-setup.mdpin examples, commit, push
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.
- 2d ago First seen · 109 lines · 50 tokens per session scan A 21294b384273
release is a skill published in the GitHub repository PyModel/designer-skill (30 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 1,225 once invoked, about $0.0003 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
changeset
Skill "changeset" from daangn/seed-design, covering changeset, 실행 절차, phase 1: 변경 패키지 감지 (후보 목록), ansi/커서 제어문자 제거 후 'changed packages' 섹션의 패키지명만 추출 and phase 2: 패키지별 bump 확정 (askuserquestion).
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
omd:release-hygiene
오픈소스 릴리스 위생 루틴. 새 기능/스킬/에이전트를 추가했을 때 (1) 부산물(v1/v2 .bak, source, 로그, scratch dir)이 changeset에 없는지, (2) 문서(README/docs/home)가 동기화됐는지, (3) npm 배포 대상인지(skills/ + files vs .claude local-preview) 판단했는지 체크리스트로 강제. '릴리스 준비', '커밋 전 점검', 'push 전에 정리', '배포 위생', 'release hygiene' 류 트리거. husky pre-commit이 부산물 게이트를 자동 실행.
release-retrospective
Produce a structured look-back after a major release or deprecation — capturing what the plan got right, what it missed, and what to do differently. Trigger when someone says: release retrospective, post-release review, what went wrong with the release, how did the deprecation go, release post-mortem, retro on the…
version-bump-advisor
Recommend the correct semver bump with reasoning and a generated changelog entry. Trigger when someone says: what version bump, is this a breaking change, semver recommendation, should this be major or minor, version this release, changelog entry, what kind of release is this, or anything about versioning a design…
qiaomu-design
偏执型设计顾问 v3.7(融合版)— Jobs 式产品直觉 + Rams 式功能纯粹主义,融合多套顶级设计 Skill 实测精华 (Anthropic frontend-design 的美学胆量、Vercel web-design-guidelines 的工程规范、taste-skill 的反模板拨盘、 Emil Kowalski 的动效工艺、ui-ux-pro-max 的准则化组件行为、IBM Carbon 的组件/模式决策框架)。 重新设计页面、审视 UI 方案、优化交互体验、从零构建界面时使用。 触发词:"重新设计"、"redesign"、"优化界面"、"优化交互"、"设计方案"、"UI 审查"、"这个页面不行"、…