MCP Gateway & Registry is a governed control plane that provides one authenticated entry point for MCP servers, AI agents, skills, and other AI assets, while supporting discovery, access control, and audit records. Organizations use it to register and manage development tools for autonomous agents and coding assistants. Catalogue add-ons operate or extend workflows around these registered AI assets.
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 agentic-community/mcp-gateway-registry --skill create-milestonegit clone --depth 1 https://github.com/agentic-community/mcp-gateway-registryWrote 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/agentic-community/mcp-gateway-registry/create-milestone)<a href="https://agentmods.dev/skills/agentic-community/mcp-gateway-registry/create-milestone"><img src="https://agentmods.dev/badge/skills/agentic-community/mcp-gateway-registry/create-milestone/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/agentic-community/mcp-gateway-registry/create-milestone"><img src="https://agentmods.dev/badge/skills/agentic-community/mcp-gateway-registry/create-milestone.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.03613 |
| Opus 5.5 | $0.00026 | $0.01445 |
| Sonnet 5.5 | $0.00013 | $0.00723 |
| Haiku 4.5 | $0.00006 | $0.00361 |
Grade A, and why
create-milestone 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 1mo 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Milestone Skill
Use this skill when the user wants to plan and create a GitHub milestone for an upcoming release. The skill identifies what has changed since a baseline release, presents a draft for approval, and creates the milestone with all approved items.
Supports creating multiple milestones in sequence (e.g., v1.0.20, v1.0.21) by letting the user choose the baseline and which items belong to which release.
Input
The skill accepts optional parameters:
/create-milestone [VERSION] [DATE] [NOTES]
- VERSION - Target version (e.g.,
v1.0.20). If not provided, suggest based on latest release. - DATE - Target release date (e.g.,
2026-04-21). If not provided, ask the user. - NOTES - Optional theme or notes (e.g., "security hardening", "federation improvements").
Output
- A GitHub milestone with description containing two tables (Issues and PRs)
- A local draft file at
.scratchpad/{version}-release-notes.mdwith detailed release notes
Workflow
Step 1: Discover Releases and Milestones
Gather the current state of releases and milestones:
# Get recent releases (tags + dates)
gh release list --limit 10 --json tagName,publishedAt,name \
--jq '.[] | "\(.tagName)\t\(.publishedAt)\t\(.name)"'
# Get existing milestones (to avoid duplicates and show what's already planned)
gh api repos/{owner}/{repo}/milestones --jq '.[] | "\(.number)\t\(.title)\t\(.due_on)\t\(.open_issues)\t\(.closed_issues)"'
# Git tags for reference
git tag --sort=-v:refname | grep '^v[0-9]' | head -10
Step 2: Ask the User What They Want
Present findings and ask the user to specify:
- Which version to create a milestone for (suggest next patch bump from latest release)
- Target date for the release
- Baseline release to diff from -- this is critical for flexibility
- Theme or notes for this release
Example prompt:
Current state:
- Latest release: v1.0.19 (published April 14, 2026)
- Existing milestones: v1.0.19 (due Apr 14, 30 closed / 3 open)
Suggested next milestone: v1.0.20
Questions:
1. What version? (default: v1.0.20)
2. What is the target release date?
3. Which release should I diff from? (default: v1.0.19, the latest)
- Other options: v1.0.18, v1.0.17, v1.0.16, ...
4. Any theme or notes? (e.g., "external registry federation")
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.
- 1mo ago First seen · 401 lines · 64 tokens per session scan A 42b913b2d1d6
create-milestone is a skill published in the GitHub repository agentic-community/mcp-gateway-registry (1,012 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 3,613 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.