cursor-feedback-extension: Skill for Cursor

.cursor/skills/releasing/SKILL.md

releasing is a skill for Cursor from jianger666/cursor-feedback-extension. It costs 39 tokens per session (547 once invoked), scanned A, original, MIT.

Release instructions for publishing the cursor-feedback package to npm, Open VSX, and the Visual Studio Code Marketplace.

In plain words
What is it for?
Preparing a release, updating the changelog and version, pushing the release tag, and checking publication on npm and Open VSX.
Why use it?
They describe the required versioning, tagging, authentication, and checks so releases follow the project's automated process.

Skill for Cursor

Written for Cursor: installed under .cursor/.

This is jianger666/cursor-feedback-extension's own configuration. It tells Cursor how to work on cursor-feedback-extension 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 cursor-feedback-extension configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jianger666/cursor-feedback-extension. 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/jianger666/cursor-feedback-extension/main/.cursor/skills/releasing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jianger666/cursor-feedback-extension

Made for: Cursor.

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 releasing

README.md
[![agentmods](https://agentmods.dev/badge/skills/jianger666/cursor-feedback-extension/releasing/github.svg)](https://agentmods.dev/skills/jianger666/cursor-feedback-extension/releasing)
Your own site
<a href="https://agentmods.dev/skills/jianger666/cursor-feedback-extension/releasing"><img src="https://agentmods.dev/badge/skills/jianger666/cursor-feedback-extension/releasing/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.

agentmods 80×15 button for releasing

Your own site · 80×15
<a href="https://agentmods.dev/skills/jianger666/cursor-feedback-extension/releasing"><img src="https://agentmods.dev/badge/skills/jianger666/cursor-feedback-extension/releasing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 547 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00039 $0.00547
Opus 5 $0.00019 $0.00273
Sonnet 5 $0.00008 $0.00109
Haiku 4.5 $0.00004 $0.00055

Measured 9d ago against content hash 2c6158141fa2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

releasing scanned grade A with 1 finding 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 9d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s https://open-vsx.org/api/jianger666/cursor-feedback | grep -o '"version":"[^"]*"'
.cursor/skills/releasing/SKILL.md · 44 lines

What it actually says

发布 cursor-feedback 新版本

发版用 standard-version 升级版本号,发布由 GitHub Actions(.github/workflows/release.yml,推送 v*.*.* tag 触发)自动完成三个渠道。不要手动 npm publish / vsce publish

发版步骤

- [ ] 1. 改动已 commit,且遵循 conventional commits(feat: / fix: / chore:)
- [ ] 2. 升级版本:npm run release:patch(或 release:minor / release:major)
- [ ] 3. 推送:git push --follow-tags origin main
- [ ] 4. 验证三渠道发布成功
  • 第 2 步standard-version 自动升级 package.json 版本、按 commit 生成 CHANGELOG、打 vX.Y.Z tag。
  • 第 3 步:推送 tag 后 GitHub Actions 自动发布,去仓库 Actions 页看进度。

两个发布渠道

渠道 认证 说明
npm OIDC Trusted Publishing 免 token、永不过期(已在 npmjs 配 trusted publisher)
Open VSX OVSX_PAT secret Cursor / Windsurf / VSCodium 用户从这装

OVSX_PAT 在 GitHub 仓库 Settings → Secrets and variables → Actions 配置。

硬约束(踩过的坑,别再犯)

  • 禁止给 package.jsonfiles 字段:会与 .vscodeignore 冲突,导致 vsce package 直接失败。npm 包瘦身只用 .npmignore,VS Code 打包只用 .vscodeignore,两者各管各的、互不影响。
  • pre-push hook 会校验 package.json 的 version 已写入 CHANGELOG.md,没写会被拦下。

验证发布

npm view cursor-feedback version
curl -s https://open-vsx.org/api/jianger666/cursor-feedback | grep -o '"version":"[^"]*"'

两个版本号都应等于刚发的版本。

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. 9d ago First seen · 44 lines · 39 tokens per session scan A 2c6158141fa2

Subscribe to this mod's changes

releasing is a skill published in the GitHub repository jianger666/cursor-feedback-extension (32 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 547 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…

addyosmani/agent-skills · 74 tokens

finishing-a-development-branch

A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.

jnMetaCode/superpowers-zh · 25 tokens

skillshare-changelog

Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…

runkids/skillshare · 134 tokens

skillshare-release

End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…

runkids/skillshare · 87 tokens

github-release-briefing-skill

Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.

FrancyJGLisboa/agent-skill-creator · 45 tokens

devops/changelog-generation

A method for creating a CHANGELOG, a document that records what changed in each software release. It reads Git commit history and release-pipeline reports, then groups changes using common commit and changelog conventions.

echoVic/boss-skill · 36 tokens