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.
git clone --depth 1 https://github.com/manuelfussTC/PulseFrameworkWrote 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/rules/manuelfusstc/pulseframework/release)<a href="https://agentmods.dev/rules/manuelfusstc/pulseframework/release"><img src="https://agentmods.dev/badge/rules/manuelfusstc/pulseframework/release/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.
<a href="https://agentmods.dev/rules/manuelfusstc/pulseframework/release"><img src="https://agentmods.dev/badge/rules/manuelfusstc/pulseframework/release.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01041 |
| Opus 5.5 | $0.00000 | $0.00416 |
| Sonnet 5.5 | $0.00000 | $0.00208 |
| Haiku 4.5 | $0.00000 | $0.00104 |
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 1mo 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.
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')" 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
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.
- 1mo ago First seen · 136 lines · 0 tokens per session scan C 843139c2ebc0
release is a cursor rule published in the GitHub repository manuelfussTC/PulseFramework (28 stars, last pushed 9mo 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.
Other cursor rules, from other repositories
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
roslyn-mcp-github-release
GitHub Releases are dispatched by a human; agents never push tags.
releasing
How to release AdLoop to PyPI — version bumping, tagging, and publishing.
05-release-preparation
Prepare a semver release (CHANGELOG, pyproject.toml, uv.lock, checks).
release
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.