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.
/plugin marketplace add sigistry/marketplacenpx agentmods add plugins/sigistry/marketplace/release-conductorgit clone --depth 1 https://github.com/sigistry/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/plugins/sigistry/marketplace/release-conductor)<a href="https://agentmods.dev/plugins/sigistry/marketplace/release-conductor"><img src="https://agentmods.dev/badge/plugins/sigistry/marketplace/release-conductor.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
release-conductor 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 yesterday.
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.
What it actually says
{
"name": "release-conductor",
"version": "1.0.0",
"description": "Owns everything around the diff: craft Conventional Commits and PR descriptions, recommend the right semver bump by reasoning about behavioral breaking changes, assemble changelogs from messy history, and guide merge-conflict resolution, rebase planning, and git-history archaeology.",
"author": {
"name": "Sigistry Release Conductor",
"url": "https://github.com/Sigistry/marketplace/tree/main/plugins/release-conductor"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 2 skills, 5 commands, 3 agents travel with it, and installing the plugin installs all of them — 424 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill breaking-change-detection A 73 tokens
- Skill changelog-assembly A 70 tokens
- Command release-notes A 20 tokens
- Command ship A 22 tokens
- Command commit A 11 tokens
- Command rebase-plan A 21 tokens
- Command resolve-conflicts A 16 tokens
- Agent git-historian A 67 tokens
- Agent semver-advisor A 67 tokens
- Agent conflict-resolver A 57 tokens
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.
- yesterday First seen · 11 lines scan A 2c5089729f73
release-conductor is a plugin published in the GitHub repository sigistry/marketplace (3 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.
Other plugins, from other repositories
ship
Git shipping workflow — conventional commits with gitmojis, PRs and MRs with the matching forge CLI, curated releases.
aidd-vcs
External artifacts: commit, pull-request, release-tag, issue-create.
open-source
Collection of skills for open-source R and Python package developers.
prflow
Turn feature requests into review-ready pull requests: issue, implementation, tests, a review-and-fix loop, and docs. Runs locally or on GitHub Actions, and is built for complex brownfield repos. Each week its retrospective reads what you actually merged and proposes improvements to your skill extensions.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.