Borrowing it
Nothing to install: this file belongs to pvliesdonk/paperless-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pvliesdonk/paperless-mcp/main/.agents/skills/releasing/SKILL.mdgit clone --depth 1 https://github.com/pvliesdonk/paperless-mcpWrote 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/skills/pvliesdonk/paperless-mcp/releasing)<a href="https://agentmods.dev/skills/pvliesdonk/paperless-mcp/releasing"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/releasing/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/skills/pvliesdonk/paperless-mcp/releasing"><img src="https://agentmods.dev/badge/skills/pvliesdonk/paperless-mcp/releasing.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.00054 | $0.03881 |
| Opus 5.5 | $0.00022 | $0.01552 |
| Sonnet 5.5 | $0.00011 | $0.00776 |
| Haiku 4.5 | $0.00005 | $0.00388 |
Grade A, and why
releasing 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing
Claude Code plugin channel
.claude-plugin/plugin/ ships this server as a Claude Code plugin: .claude-plugin/plugin.json (identity + version) and an exec-form .mcp.json that launches the released PyPI package with uvx --from <pkg>==<version>. Both manifests are version-coupled to the stable release stream — scripts/stamp_manifests.py stamps and stages them inside each stable release PR, so the marketplace entry published by the release workflow always installs the version it points at. That entry is written into the catalog's .claude-plugin/marketplace.json, the only path Claude Code loads a marketplace from — a manifest anywhere else is not a marketplace, and the publish job fails rather than bumping one. The marketplace entry is a rolling pointer, so on rc prepares the script leaves both files at the last published stable rather than pointing everyone browsing the catalog at a candidate (tests/test_release_flow_contract.py gates the invocation pairing and this skip). The env block in .mcp.json, the plugin README, and any skills/ directories are project-owned content: the files are seeded once and never re-rendered by template updates. Values in env may reference plugin userConfig entries as ${user_config.<id>} declared in plugin.json — exec-form fields only; shell-form command strings reject the substitution.
To generate the plugin's configuration screen from the config surface instead of hand-editing it, declare a files: pair in config-presentation.domain.yml: the plugin.json path with kind: claude-plugin-user-config and a fields: map (same field specs as the mcpb install screen (see the config-contract skill)), plus the .mcp.json path with kind: claude-plugin-env and fields_from: naming the first entry. One fields map then drives both the userConfig object and the ${user_config.<id>} env wiring, and scripts/gen_config_surface.py --check gates the pair against drift.
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.
- 25d ago Changed f1387364974c
- 1mo ago First seen · 97 lines · 54 tokens per session scan A 472140a61be2
releasing is a skill published in the GitHub repository pvliesdonk/paperless-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 3,881 once invoked, about $0.0002 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-09-16.
Other skills, from other repositories
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…