agentmods.dev

Figma-Context-MCP: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from stone-w4tch3r/Figma-Context-MCP. It costs 0 tokens per session (311 once invoked), scanned A, original, MIT.

A release command for Framelink MCP for Figma, an MCP server that gives AI coding tools access to Figma design data. It guides the process of reviewing and merging an automated release pull request.

In plain words
What is it for?
Use it to find a release-please pull request, inspect its changes, request confirmation, merge it, and verify that the npm publishing workflow started.
Why use it?
It turns the release process into a checked sequence, so the pending version, changelog, included commits, and publishing workflow are reviewed before merging.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the AskUserQuestion tool.

This is stone-w4tch3r/Figma-Context-MCP's own configuration. It tells Claude Code how to work on Figma-Context-MCP itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Figma-Context-MCP configures →

not rated 29repo 2mo ago A scan 0 tokens original MIT
View source ↗ stone-w4tch3r/Figma-Context-MCP framelink.ai
Reuse

Borrowing it

Nothing to install: this file belongs to stone-w4tch3r/Figma-Context-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/stone-w4tch3r/Figma-Context-MCP/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/stone-w4tch3r/Figma-Context-MCP

Made for: Claude Code.

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 release

README.md
[![agentmods](https://agentmods.dev/badge/commands/stone-w4tch3r/figma-context-mcp/release.svg)](https://agentmods.dev/commands/stone-w4tch3r/figma-context-mcp/release)
Your own site
<a href="https://agentmods.dev/commands/stone-w4tch3r/figma-context-mcp/release"><img src="https://agentmods.dev/badge/commands/stone-w4tch3r/figma-context-mcp/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 311 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 original No closer match found 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.00000 $0.00311
Opus 5 $0.00000 $0.00156
Sonnet 5 $0.00000 $0.00062
Haiku 4.5 $0.00000 $0.00031

Measured 7d ago against content hash 7380c25048c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 7d 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

Copies of this mod

1 near-identical copy found in the catalogue:

  • release — 100% identical, 0 lines differ
.claude/commands/release.md · 32 lines

What it actually says

Release

Review and publish a new release.

Steps

  1. Check for a release-please PR: Run gh pr list --repo GLips/Figma-Context-MCP --label "autorelease: pending" --json number,title,url to find the open release PR.

    If no release PR exists, inform the user: "No pending release PR. Release-please creates one automatically when conventional commits (fix:, feat:) land on main."

  2. Show what's in the release: Run gh pr view <number> --json body to display the pending changelog and version bump. Summarize:

    • New version number
    • Number of features, fixes, and other changes
    • List of included commits

  3. Ask for confirmation: Use AskUserQuestion: "Merge this release PR to publish v to npm?"

    • Merge and publish — Proceed with merge
    • Review diff first — Show gh pr diff <number>
    • Cancel — Stop without merging

  4. Merge the release PR: Run gh pr merge <number> --squash --repo GLips/Figma-Context-MCP

  5. Verify: Run gh run list --repo GLips/Figma-Context-MCP --limit 1 to confirm the Release workflow triggered. Report the workflow run URL so the user can monitor npm publish.

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. 7d ago First seen · 32 lines · 0 tokens per session scan A 7380c25048c6

Subscribe to this mod's changes

release is a command published in the GitHub repository stone-w4tch3r/Figma-Context-MCP (29 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 311 tokens. 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.

Git and workflowReleases
Related

Other commands, from other repositories

land

Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).

gmickel/flow-next · 25 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

ship

Ship is the operational release-prep flow for a connected project repo.

robotaitai/project-bedrock · 0 tokens

release-plan

A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.

alisunstar/OpenSunstar · 0 tokens

release

Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.

terrene-foundation/kailash-coc-claude-py · 0 tokens

create-pr

Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.

dsswift/ion · 25 tokens