What is siyuan-plugin-pub?

A release procedure for publishing the SiYuan Sisyphus plugin, its standalone command-line tool, or both. It covers versioning, release notes, contributor credits, documentation, tags, and npm publishing preparation.

It helps classify the release, update the appropriate product files, prepare notes and documentation, credit merged-PR contributors, create tags, and prepare npm publication.

It prevents the plugin and command-line package from being released under the wrong path or with inconsistent version and publishing details.

How yangtaihong59/siyuan-plugins-mcp-sisyphus configures Claude Code a

Reuse

Borrowing it

Nothing to install: this file belongs to yangtaihong59/siyuan-plugins-mcp-sisyphus. 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/yangtaihong59/siyuan-plugins-mcp-sisyphus/main/.agents/skills/siyuan-plugin-pub/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/yangtaihong59/siyuan-plugins-mcp-sisyphus

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yangtaihong59/siyuan-plugins-mcp-sisyphus/siyuan-plugin-pub/github.svg)](https://agentmods.dev/skills/yangtaihong59/siyuan-plugins-mcp-sisyphus/siyuan-plugin-pub)

Your own site

<a href="https://agentmods.dev/skills/yangtaihong59/siyuan-plugins-mcp-sisyphus/siyuan-plugin-pub"><img src="https://agentmods.dev/badge/skills/yangtaihong59/siyuan-plugins-mcp-sisyphus/siyuan-plugin-pub/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yangtaihong59/siyuan-plugins-mcp-sisyphus/siyuan-plugin-pub"><img src="https://agentmods.dev/badge/skills/yangtaihong59/siyuan-plugins-mcp-sisyphus/siyuan-plugin-pub.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,085 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.04085
Opus 5	$0.00025	$0.02042
Sonnet 5	$0.00010	$0.00817
Haiku 4.5	$0.00005	$0.00409

Measured 13d ago against content hash ae27ce76fbb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

siyuan-plugin-pub 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 13d 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.

.agents/skills/siyuan-plugin-pub/SKILL.md · 369 lines

How it starts

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

SiYuan Plugin Pub

Use this skill when the user wants to publish a new version of this SiYuan Sisyphus repo. The repo ships two related but independently versioned products:

SiYuan plugin / MCP server: marketplace plugin metadata and bundled dist/mcp-server.cjs
Standalone CLI: npm package siyuan-sisyphus, with siyuan-sisyphus and siyuan binaries

Release Type Gate

Before editing release files, classify the request as exactly one path.

Use the user's explicit wording first. If they do not specify a release type, infer from mentioned features and changed files:

plugin-only: plugin UI, MCP server, non-CLI docs, marketplace metadata, or plugin-only fixes changed.
CLI-only: src/cli/, cli/, CLI install/config/rendering behavior, npm package docs, or CLI publish docs changed.
combined: shared tool/API behavior changed in src/api/, src/core/, src/tools/, or the user wants both the plugin and npm CLI published.

If a required version number is missing, stop and ask for it.

If the release type is still unclear after checking the request and git status --short, state the inferred path and ask for confirmation before changing versions.

This repo already keeps release metadata, fallback versions, and release notes in:

plugin.json
package.json
src/core/feedback.ts
CHANGELOG.md
README.md
README_zh_CN.md
cli/package.json
cli/README.md
cli/README_zh_CN.md
docs/development/release-cli.md
docs/zh/development/release-cli.md

Repo-Specific Rules

Keep plugin versions in plugin.json and root package.json on the exact same version string such as 0.3.4.
Keep the feedback tool fallback version in src/core/feedback.ts (FEEDBACK_PLUGIN_VERSION) on the same plugin version. It is used when the compiled __PLUGIN_VERSION__ define is unavailable.
Keep CLI version in cli/package.json independent from the plugin version, such as 0.1.5. Do not force it to match the plugin version.
CHANGELOG.md is the source of truth for plugin release notes and uses Chinese entries with newest plugin version on top.
When a release contains merged PRs, identify each PR author from PR metadata and explicitly thank them in both CHANGELOG.md and the settings changelog (public/i18n/zh_CN.json and public/i18n/en_US.json). Never write only the PR number or a generic “thanks for the contribution.”
Use the contributor's GitHub login, not the merge committer or an inferred display name. Prefer GitHub PR metadata; use the merge commit author only as a fallback when PR metadata is unavailable, and state that the attribution was inferred before publishing.
README.md and README_zh_CN.md both maintain the latest plugin version callout near the top; update both for plugin releases.
cli/README.md and cli/README_zh_CN.md describe standalone CLI usage; update them when CLI behavior, install flow, or command syntax changes.
docs/development/release-cli.md and docs/zh/development/release-cli.md are the CLI publish docs; keep them aligned when release procedure changes.
Prefer matching the repo's recent commit style, for example:
- feat：新增文档头图与本地上传确认流程，整理代码并发布 v0.1.11
- feat：优化 MCP tool 行为一致性并发布 v0.1.10
Do not run git tag or git push until the user explicitly wants to execute publish commands.

Read the full file on GitHub · 369 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.

13d ago First seen · 369 lines · 50 tokens per session scan A ae27ce76fbb0

Subscribe to this mod's changes

siyuan-plugin-pub is a skill published in the GitHub repository yangtaihong59/siyuan-plugins-mcp-sisyphus (104 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 4,085 once invoked, about $0.0003 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-30.

Git and workflow Releases

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

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.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

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.

phuryn/pm-skills · 57 tokens

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.

aeonfun/aeon · 27 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens

siyuan-plugins-mcp-sisyphus: Skill for Claude Code