agentmods.dev

release-workflow

A release checklist and versioning guide for the buda-mcp project, which connects AI assistants to Buda.com market data.

In plain words
What is it for?
Use it when preparing and publishing a new buda-mcp release, including updating files, running tests, tagging the release, and publishing packages.
Why use it?
It helps prevent missed version updates, failed tests, incomplete marketplace listings, and publishing mistakes.

Cursor rule for Cursor

0 2mo ago A scan 662 tokens original MIT
View the source file gtorreal/buda-mcp
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/gtorreal/buda-mcp/release-workflow
Clone the repo
git clone --depth 1 https://github.com/gtorreal/buda-mcp

Made for: Cursor.

Per session 662 This file is loaded in full into every session.
When invoked 662 The same file — it is already loaded in full.
Security scan A 0 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.00662 $0.00662
Opus 5 $0.00331 $0.00331
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

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

Security

Grade A, and why

release-workflow 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 2d 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.

.cursor/rules/release-workflow.mdc · 54 lines

How it starts

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

buda-mcp Release Workflow

Version source-of-truth

  • package.json is the only place to set the version number.
  • After changing it, always run npm run sync-version to propagate it to server.json.
  • All runtime references (User-Agent, McpServer, health endpoint, server-card) read from src/version.ts — never hardcode version strings.

Before publishing a new version

  1. Bump package.json version
  2. npm run sync-version — updates server.json
  3. npm test — must pass (23 unit + all integration)
  4. Update CHANGELOG.md with all changes since the last release
  5. Update marketplace/ files if tools were added/changed/removed:
    • marketplace/gemini-tools.json — function declarations
    • marketplace/openapi.yaml — version field + path descriptions
    • marketplace/claude-listing.md — tool descriptions
    • marketplace/README.md — version header
  6. Update PUBLISH_CHECKLIST.md with new version and release notes template
  7. Commit and push

Publishing steps (manual, done after development is complete)

npm publish --access public --provenance   # → npmjs.com
# then create GitHub Release tag vX.Y.Z → triggers Actions workflow (MCP registry auto-publish)
# then notify mcp.so and Glama.ai — templates in PUBLISH_CHECKLIST.md

Adding a new tool

  1. Create src/tools/<name>.ts
  2. Export toolSchema (name, description, inputSchema) — picked up automatically by http.ts server-card
  3. Export register(server, client, cache?)
  4. For tools with destructive actions: export the handler function for unit testing
  5. Apply validateMarketId if the tool accepts market_id
  6. Register in both src/index.ts and src/http.ts
  7. Add to marketplace/gemini-tools.json, marketplace/openapi.yaml, marketplace/claude-listing.md
  8. Add unit tests in test/unit.ts

Key architecture notes

  • src/validation.ts — validateMarketId(id) returns error string or null; apply before .toLowerCase() and URL use
  • src/cache.ts — MemoryCache with in-flight deduplication; TTLs: markets 60s, tickers 5s, orderbooks 3s
  • BudaApiError has retryAfterMs for 429 responses; client retries once honoring Retry-After header (seconds, RFC 7231, default 1s, capped at 30s)
  • scripts/sync-version.mjs — run via npm run sync-version
  • Unit tests: npm run test:unit (no network); Integration: npm run test:integration (skips if API unreachable)

Read the full file on GitHub · 54 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. 2d ago First seen · 54 lines · 662 tokens per session scan A f3699f1eac86

Subscribe to this mod's changes

release-workflow is a cursor rule published in the GitHub repository gtorreal/buda-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 662 tokens to every session, about $0.0033 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.

Git and workflowReleases
Related

Other cursor rules, from other repositories

08-github-workflow-standards

GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).

MarcoPorcellato/matryca-plumber · 21 tokens

release-notes

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

thatrebeccarae/claude-marketing · 50 tokens

versioning

Semantic versioning rules for tagging releases.

git-treeline/cli · 324 tokens

versioning-and-npm-distribution

Versioning integrity and GitHub/npm distribution flow for AgentProdReady.

ameenmari/agentprodready · 449 tokens

release-checklist

What to update with each code change or version release.

yoreai/relay · 215 tokens

release

Cut a versioned release of harness-mini — bump VERSION, roll the CHANGELOG, tag, and publish a GitHub release. Use when shipping a new version. Wraps bin/harness.sh release; covers the human-judgment steps (semver choice, changelog curation) the script can't make.

harness-mini/harness-mini · 64 tokens