Borrowing it
Nothing to install: this file belongs to pvliesdonk/scholar-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/scholar-mcp/main/.agents/skills/releasing/SKILL.mdgit clone --depth 1 https://github.com/pvliesdonk/scholar-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/scholar-mcp/releasing)<a href="https://agentmods.dev/skills/pvliesdonk/scholar-mcp/releasing"><img src="https://agentmods.dev/badge/skills/pvliesdonk/scholar-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/scholar-mcp/releasing"><img src="https://agentmods.dev/badge/skills/pvliesdonk/scholar-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.03591 |
| Opus 5 | $0.00027 | $0.01795 |
| Sonnet 5 | $0.00011 | $0.00718 |
| Haiku 4.5 | $0.00005 | $0.00359 |
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 today.
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.
This is a copy
95% identical to releasing — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 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.
- today Changed ae56f6ff8f97
- yesterday First seen · 77 lines · 54 tokens per session scan A a1a34688d19e
releasing is a skill published in the GitHub repository pvliesdonk/scholar-mcp (2 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 3,591 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to releasing, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.