release

A release checklist for the PULSE project. It covers publishing the command-line tool, server, code-editor extension, and source repository together.

In plain words
What is it for?
Checking versions, building and publishing packages, publishing the extension, and pushing the corresponding repository changes.
Why use it?
It helps prevent users from receiving mismatched versions of the project's components.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/manuelfusstc/pulseframework/release
Clone the repo
git clone --depth 1 https://github.com/manuelfussTC/PulseFramework

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,041 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
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 $0.00000 $0.01041
Opus 5 $0.00000 $0.00521
Sonnet 5 $0.00000 $0.00208
Haiku 4.5 $0.00000 $0.00104

Measured yesterday against content hash 843139c2ebc0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

release scanned grade C with 2 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 yesterday.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

echo "Ext: $(curl -s 'https://open-vsx.org/api/pulse-framework/pulse-framework' | node -p 'JSON.parse(require(\"fs\").readFileSync(0)).version')"

Makes network callslowCapability

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

echo "Ext: $(curl -s 'https://open-vsx.org/api/pulse-framework/pulse-framework' | node -p 'JSON.parse(require(\"fs\").readFileSync(0)).version')"
.cursor/rules/release.mdc · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

📦 PULSE Release Checklist

⛔ CRITICAL RULE: ALL ARTIFACTS MUST BE IN SYNC

NEVER release only one component. ALL must be updated together:

CLI (npm)     ←→  MCP (npm)     ←→  Extension (OpenVSX)  ←→  Git (repo)
    ↑________________↑___________________↑____________________↑
                        ALL MUST MATCH

Before ANY release, check sync:

echo "CLI: $(npm view pulse-framework-cli version)"
echo "MCP: $(npm view pulse-framework-mcp version)"
echo "Ext: $(curl -s 'https://open-vsx.org/api/pulse-framework/pulse-framework' | node -p 'JSON.parse(require(\"fs\").readFileSync(0)).version')"

Components to Update

Component Location Publish Command
Git Repo GitHub git push
CLI (npm) packages/pulse-cli npm publish
MCP (npm) packages/pulse-mcp npm publish
Extension (OpenVSX) packages/pulse-vscode npx ovsx publish

🔄 Release Flow

1. CLI Changes (packages/pulse-cli)

# 1. Bump version in package.json
# 2. Build
cd packages/pulse-cli
npm run build

# 3. Publish to npm
npm publish --access public

# 4. Commit & push
git add -A && git commit -m "feat(cli): description - vX.Y.Z"
PULSE_ALLOW_PUSH=1 git push

2. MCP Changes (packages/pulse-mcp)

# 1. Bump version in package.json
# 2. Build
cd packages/pulse-mcp
npm run build

# 3. Publish to npm
npm publish --access public

# 4. Commit & push
git add -A && git commit -m "feat(mcp): description - vX.Y.Z"
PULSE_ALLOW_PUSH=1 git push

3. Extension Changes (packages/pulse-vscode)

# 1. Bump version in package.json AND extension.ts CURRENT_VERSION
# 2. Update CHANGELOG.md
# 3. Build & typecheck
cd packages/pulse-vscode
npm run build && npm run typecheck

# 4. Package
npx @vscode/vsce package --no-dependencies

# 5. Publish to OpenVSX
npx ovsx publish pulse-framework-X.Y.Z.vsix -p $OVSX_TOKEN

# 6. Commit & push
git add -A && git commit -m "feat(extension): description - vX.Y.Z"
PULSE_ALLOW_PUSH=1 git push

Read the full file on GitHub · 136 lines

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. yesterday First seen · 136 lines · 0 tokens per session scan C 843139c2ebc0

Subscribe to this mod's changes

release is a cursor rule published in the GitHub repository manuelfussTC/PulseFramework (28 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,041 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.