mcp-wallet-signer: Skill for Claude Code

.claude/skills/publish/SKILL.md

publish is a skill for Claude Code from nikicat/mcp-wallet-signer. It costs 23 tokens per session (483 once invoked), scanned A, original, MIT.

A release workflow for publishing packages from a monorepo, a repository that contains multiple related packages. It bumps the version, builds the selected package, publishes to its supported registries, and creates a GitHub release.

In plain words
What is it for?
Use it to release mcp-wallet-signer, browser-evm-signer, or browser-tron-signer with a patch, minor, or major version change.
Why use it?
It organizes the release steps and prevents internal-only packages from being published as consumer packages.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is nikicat/mcp-wallet-signer's own configuration. It tells Claude Code how to work on mcp-wallet-signer 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 mcp-wallet-signer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nikicat/mcp-wallet-signer. 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/nikicat/mcp-wallet-signer/master/.claude/skills/publish/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/nikicat/mcp-wallet-signer

Made for: Claude Code.

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 publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/nikicat/mcp-wallet-signer/publish/github.svg)](https://agentmods.dev/skills/nikicat/mcp-wallet-signer/publish)
Your own site
<a href="https://agentmods.dev/skills/nikicat/mcp-wallet-signer/publish"><img src="https://agentmods.dev/badge/skills/nikicat/mcp-wallet-signer/publish/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 publish

Your own site · 80×15
<a href="https://agentmods.dev/skills/nikicat/mcp-wallet-signer/publish"><img src="https://agentmods.dev/badge/skills/nikicat/mcp-wallet-signer/publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 483 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.
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.00023 $0.00483
Opus 5.5 $0.00009 $0.00193
Sonnet 5.5 $0.00005 $0.00097
Haiku 4.5 $0.00002 $0.00048

Measured 1mo ago against content hash d89b5c33ff45, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

publish 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 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.

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.

.claude/skills/publish/SKILL.md · 41 lines

What it actually says

Publish a package from this repo via GitHub release. Everything here is a compatibility shim over browser-web3-signer — releases should be rare, and only to keep an existing install working.

Arguments are optional and positional:

  • package: mcp-wallet-signer, browser-evm-signer, or browser-tron-signer
  • bump: patch, minor, or major

Infer a missing package from git diff HEAD~3 --stat -- packages/; if ambiguous, ask.

Steps

  1. Bump version in packages/<package>/package.json (and version + packages[0].version in the root server.json for mcp-wallet-signer, which the MCP registry reads).
  2. npm test at the repo root — builds every package and runs each one's tests.
  3. Commit, push, then gh release create <package>@<version> --title <package>@<version> --notes …. The publish.yml workflow parses the tag, checks the version matches the package.json, and publishes that one workspace.

npm auth

Trusted publishing (OIDC) — there are no tokens in this repo. Each package lists provider GitHub Actions, owner nikicat, repo mcp-wallet-signer, workflow publish.yml, environment blank, under its npmjs.com "Access → Trusted Publishers". npm publish --provenance in the workflow authenticates through id-token: write and npm generates the provenance attestation.

Renaming publish.yml breaks this — update the trusted publisher on npmjs.com first, or the publish fails with ENEEDAUTH.

JSR

browser-evm-signer and browser-tron-signer used to publish to JSR as @nikicat/browser-*-signer. The shims are npm-only; the JSR packages are frozen at their last Deno release.

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. 1mo ago Changed · -117 lines · -4 tokens per session scan C → A d89b5c33ff45
  2. 2mo ago First seen · 158 lines · 27 tokens per session scan C 6cae12a6746d

Subscribe to this mod's changes

publish is a skill published in the GitHub repository nikicat/mcp-wallet-signer (2 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 483 once invoked, about $0.0001 per session on Opus 5.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.

Related

publish compared with skills from other repositories

publish next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
publishnikicat/mcp-wallet-signerSkill26d agoMITA23Claude Code
git-workflowhiromaily/go-crypto-walletSkill1286mo agoMITA31Claude Code
fix-pr-reviewhiromaily/go-crypto-walletSkill1286mo agoMITA26Claude Code
db-migrationhiromaily/go-crypto-walletSkill1286mo agoMITA29Claude Code
github-issue-creationhiromaily/go-crypto-walletSkill1286mo agoMITA28Claude Code
git-wrapupcyanheads/coingecko-mcp-serverSkill120d agoApache-2.0A109Claude Code
release-and-publishcyanheads/coingecko-mcp-serverSkill120d agoApache-2.0A155Claude Code