Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add davistroy/claude-marketplace --skill release-plugingit clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/davistroy/claude-marketplace/release-plugin)<a href="https://agentmods.dev/skills/davistroy/claude-marketplace/release-plugin"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/release-plugin/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/davistroy/claude-marketplace/release-plugin"><img src="https://agentmods.dev/badge/skills/davistroy/claude-marketplace/release-plugin.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.00035 | $0.02443 |
| Opus 5 | $0.00017 | $0.01222 |
| Sonnet 5 | $0.00007 | $0.00489 |
| Haiku 4.5 | $0.00003 | $0.00244 |
Grade A, and why
release-plugin 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 6d 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Plugin
Automated pre-flight checks and shipping workflow. Executes validation, cleanup, and git workflow in sequence, stopping only when user intervention is required.
Input Validation
Optional Arguments:
--skip-validate- Skip plugin validation phase--skip-cleanup- Skip repository cleanup phase--skip-ship- Run validation and cleanup only, do not proceed to shipping. Useful for pre-flight checks without committing changes.--dry-run- Preview all phases without executing changes<branch-name>- Custom branch name for shipping (passed to ship phase)
Dry-Run Mode:
When --dry-run is specified:
- Run validation (read-only, always safe)
- Preview cleanup changes without executing
- Preview ship operations without executing
- Prefix all output with
[DRY-RUN]
Delegation Mechanism
This skill orchestrates three existing capabilities in sequence. It does not delegate to subagents -- it executes each phase inline within the current session:
| Phase | Delegates To | How |
|---|---|---|
| Phase 1: Validate | /validate-plugin --all |
Runs the full validation logic inline (same session) |
| Phase 2: Cleanup | /clean-repo |
Runs the cleanup logic inline (same session) |
| Phase 3: Ship | /ship |
Runs the ship workflow inline (same session) |
Each phase runs sequentially. The output of one phase determines whether the next phase executes. If a phase fails with blocking errors, the workflow stops and reports the failure. Non-blocking warnings are logged but do not stop progression.
Workflow Overview
Phase 1: Validate --> Phase 2: Clean Repo --> Phase 3: Ship
| | |
v v v
STOP if errors Continue with Full ship
CONTINUE if warnings artifact cleanup workflow
Execution
Execute each phase in sequence. Only stop for blocking issues that require user intervention.
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.
- 6d ago First seen · 399 lines · 35 tokens per session scan A 364ce625bd13
release-plugin is a skill published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 2,443 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-09-04.
Other skills, from other repositories
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.