Borrowing it
Nothing to install: this file belongs to felixAnhalt/figma-to-code-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.
curl -O https://raw.githubusercontent.com/felixAnhalt/figma-to-code-mcp/main/.opencode/skills/release-process/SKILL.mdgit clone --depth 1 https://github.com/felixAnhalt/figma-to-code-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/skills/felixanhalt/figma-to-code-mcp/release-process)<a href="https://agentmods.dev/skills/felixanhalt/figma-to-code-mcp/release-process"><img src="https://agentmods.dev/badge/skills/felixanhalt/figma-to-code-mcp/release-process.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.1 | $0.00023 | $0.00405 |
| Opus 5 | $0.00012 | $0.00202 |
| Sonnet 5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
release-process 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.
What it actually says
What I do
I know the release process for the Figma-Context-MCP npm package.
Trigger
Push to main branch triggers .github/workflows/release.yml.
Workflow steps
-
Release Please (
googleapis/release-please-action@v4)- Opens/updates a release PR
- Follows
release-please-config.json(node release-type, bump-minor-pre-major) - Updates version in
package.jsonand.release-please-manifest.json - Generates/updates
CHANGELOG.md
-
If release created:
- Sets up pnpm 10.10.0, Node 24
- Runs
pnpm type-check - Runs
pnpm build - Publishes to npm:
pnpm publishwithNPM_CONFIG_PROVENANCE=true - Updates
server.jsonversion withjq - Publishes to MCP Registry via
mcp-publisherCLI
Version locations
package.json—versionfield (e.g., "0.28.1")server.json—versionfield (e.g., "0.14.0") — sync'd by release workflow.release-please-manifest.json—{".": "0.28.1"}— updated by release-please
Configuration files
release-please-config.json— release-type: node, changelog-path, bump-minor-pre-majorserver.json— MCP registry manifest (name, description, packages, env vars)
When to use me
Use this when:
- Preparing a release
- Debugging CI/release failures
- Understanding the version sync between package.json and server.json
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.
- 7d ago First seen · 49 lines · 23 tokens per session scan A 4a038cdeec48
release-process is a skill published in the GitHub repository felixAnhalt/figma-to-code-mcp (5 stars, last pushed 10d ago), licensed MIT. It adds 23 tokens to every session and 405 once invoked, about $0.0001 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-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.