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 buildinternet/releasesnpx agentmods add plugins/buildinternet/releases/registry-maintenancegit clone --depth 1 https://github.com/buildinternet/releasesWrote 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/buildinternet/releases/registry-maintenance)<a href="https://agentmods.dev/plugins/buildinternet/releases/registry-maintenance"><img src="https://agentmods.dev/badge/plugins/buildinternet/releases/registry-maintenance.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
registry-maintenance 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": "registry-maintenance",
"source": "./",
"description": "Operator skills for maintaining the registry — ingest, backfills, overviews, release content, playbooks, coverage. Most need an admin API key.",
"author": {
"name": "Build Internet"
},
"version": "0.1.0",
"strict": false,
"skills": [
"./.claude/skills/local-ingest",
"./.claude/skills/backfilling-sources",
"./.claude/skills/maintaining-orgs",
"./.claude/skills/regenerating-overviews",
"./.claude/skills/generating-release-content",
"./.claude/skills/seeding-playbooks",
"./.claude/skills/grouping-releases",
"./.claude/skills/firecrawl-monitoring"
]
}What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 706 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill maintaining-orgs A 54 tokens
- Skill regenerating-overviews A 54 tokens
- Skill generating-release-content A 143 tokens
- Skill local-ingest A 100 tokens
- Skill seeding-playbooks A 78 tokens
- Skill backfilling-sources A 94 tokens
- Skill firecrawl-monitoring A 92 tokens
- Skill grouping-releases A 91 tokens
What ships with it
1 file beside marketplace.json#registry-maintenance in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 20 lines scan A 38874880d734
registry-maintenance is a plugin published in the GitHub repository buildinternet/releases (6 stars, last pushed yesterday), licensed Apache-2.0. 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
releases
Search changelogs and look up releases via the hosted Releases.sh registry. Bundles the hosted MCP connection, the /releases lookup command, and auto-triggering skills for release/changelog questions.
maintainer-suite
Optional maintainer toolkit for skill review, repository publication, releases, and project announcements.
open-source
Collection of skills for open-source R and Python package developers.
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.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
release-conductor
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.