sbox-mcp-documentation: Skill for Claude Code

.github/skills/publishing/SKILL.md

publishing is a skill for Claude Code from fiedlermarius/sbox-mcp-documentation. It costs 44 tokens per session (486 once invoked), scanned A, original, MIT.

Release instructions for publishing the documentationmcp package to npm, the package registry for JavaScript and Node.js software. They cover versioning, building, publishing, and Git tagging.

In plain words
What is it for?
Use them when releasing a new npm version, verifying the package, or triggering its automated GitHub release workflow.
Why use it?
They provide a repeatable release process and help ensure that published versions and source-code tags stay aligned.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

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

Reuse

Borrowing it

Nothing to install: this file belongs to fiedlermarius/sbox-mcp-documentation. 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/fiedlermarius/sbox-mcp-documentation/main/.github/skills/publishing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/fiedlermarius/sbox-mcp-documentation

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 publishing

README.md
[![agentmods](https://agentmods.dev/badge/skills/fiedlermarius/sbox-mcp-documentation/publishing.svg)](https://agentmods.dev/skills/fiedlermarius/sbox-mcp-documentation/publishing)
Your own site
<a href="https://agentmods.dev/skills/fiedlermarius/sbox-mcp-documentation/publishing"><img src="https://agentmods.dev/badge/skills/fiedlermarius/sbox-mcp-documentation/publishing.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 486 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.00044 $0.00486
Opus 5 $0.00022 $0.00243
Sonnet 5 $0.00009 $0.00097
Haiku 4.5 $0.00004 $0.00049

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

Security

Grade A, and why

publishing 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 8d 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.

.github/skills/publishing/SKILL.md · 54 lines

What it actually says

Publishing documentation_mcp

When to Use

  • Releasing a new version of the package to npm
  • After user-facing changes that require a version bump
  • To verify the published package on npmjs.com

Procedure

  1. Ensure a clean state — all changes committed, no uncommitted files
  2. Bump the version and create a git tag (choose one):
    npm version patch   # bug fixes  → v0.1.x
    npm version minor   # new features → v0.x.0
    npm version major   # breaking changes → vx.0.0
    
    This updates package.json, commits the change, and creates a vX.Y.Z git tag automatically.
  3. Push the commit and tag:
    git push --follow-tags
    
    This triggers the GitHub Actions release workflow which:
    • Builds the package
    • Publishes to npm via OIDC (no secrets required)
    • Creates a GitHub Release with auto-generated release notes

Manual publish (fallback)

If CI is not set up or you want to publish locally:

npm run build ; npm publish

First-time setup

This workflow uses npm Trusted Publishing (OIDC) — no secrets or tokens needed in GitHub.

One-time configuration on npmjs.com:

  1. Go to npmjs.com/package/sbox-mcp-documentation → Settings → Trusted Publishing
  2. Select GitHub Actions and fill in the repository details to allow the release workflow to publish on your behalf.

Notes

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. 8d ago First seen · 54 lines · 44 tokens per session scan A d32970a8c28d

Subscribe to this mod's changes

publishing is a skill published in the GitHub repository fiedlermarius/sbox-mcp-documentation (11 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 486 once invoked, about $0.0002 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.