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 commands/nludd25/figma-context-mcp/releasegit clone --depth 1 https://github.com/nludd25/Figma-Context-MCPWrote 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/commands/nludd25/figma-context-mcp/release)<a href="https://agentmods.dev/commands/nludd25/figma-context-mcp/release"><img src="https://agentmods.dev/badge/commands/nludd25/figma-context-mcp/release.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00590 |
| Opus 5 | $0.00000 | $0.00295 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
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 3d 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.
This is a copy
100% identical to release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Review and publish a new release.
Steps
-
Check for a release-please PR: Run
gh pr list --repo GLips/Figma-Context-MCP --label "autorelease: pending" --json number,title,urlto 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 onmain." -
Show what's in the release: Run
gh pr view <number> --json bodyto display the pending changelog and version bump. Summarize:- New version number
- Number of features, fixes, and other changes
- List of included commits
-
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
-
Merge the release PR: Run
gh pr merge <number> --rebase --repo GLips/Figma-Context-MCP(or merge via the GitHub UI).Use rebase, not squash. Feature PRs are squash-merged (so each conventional-commit title, with its
(#NNN), feeds the changelog), but the release PR is the singlechore(main): release X.Y.Zcommit release-please authored. Rebase replays it ontomainverbatim — bot authorship, clean subject, no(#NNN). Squash would rewrite all three and diverge from every prior release (checkgit logforchore(main): releasecommits — they're all single-parent, bot-authored, no PR suffix). Merging through the UI does the same thing. -
Verify: Run
gh run list --repo GLips/Figma-Context-MCP --limit 1to confirm the Release workflow triggered. Report the workflow run URL so the user can monitor npm publish.The Release workflow also bumps
server.jsonand publishes to npm (OIDC) and the MCP registry — all hands-off. No manual steps beyond merging the PR. -
Write the curated release notes: Once the workflow has published the GitHub Release (the tag exists), run
/release-notesto replace the mechanical, auto-generated Release body with brand-voice highlights. release-please only produces a terse commit-title list;/release-notesturns it into something worth reading.CHANGELOG.mdis left as-is — release-please owns it.
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.
- 3d ago First seen · 48 lines · 0 tokens per session scan A 1357be5e3538
release is a command published in the GitHub repository nludd25/Figma-Context-MCP (0 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 590 tokens. A static security scan graded it A with 0 findings. It is 100% identical to release, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
ship
Deliver the increment. Then go live with a rollback you have run.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
release-tag
Create and push a version tag after a release PR has been merged.
release
Orchestrate a complete release workflow with quality gates, version bumping, and publishing automation.