Jarvis Registry is a gateway that connects AI copilots and autonomous agents to enterprise tools through the Model Context Protocol and agent-to-agent communication. Organizations use it to manage identity, permissions, tool discovery, orchestration, logging, and observability, while the catalogue entries support agent workflows with it.
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 ascending-llc/jarvis-registry --skill release-notes-checkgit clone --depth 1 https://github.com/ascending-llc/jarvis-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/ascending-llc/jarvis-registry/release-notes-check)<a href="https://agentmods.dev/skills/ascending-llc/jarvis-registry/release-notes-check"><img src="https://agentmods.dev/badge/skills/ascending-llc/jarvis-registry/release-notes-check/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/ascending-llc/jarvis-registry/release-notes-check"><img src="https://agentmods.dev/badge/skills/ascending-llc/jarvis-registry/release-notes-check.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.00016 | $0.00127 |
| Opus 5.5 | $0.00006 | $0.00051 |
| Sonnet 5.5 | $0.00003 | $0.00025 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
release-notes-check 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.
What it actually says
Release notes check
Review only the release-note text supplied by the user. Do not fetch data, run commands, or change files.
Report whether the note names an owner and contains a rollback note. Quote the supplied text for each finding. If either item is absent, write "Not provided" rather than inventing it.
Use the checklist in references/checklist.md. This is sample revision 1, not a production approval policy.
What ships with it
1 file beside SKILL.md 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.
- today First seen · 15 lines · 16 tokens per session scan A fcded0bbd5dc
release-notes-check is a skill published in the GitHub repository ascending-llc/jarvis-registry (3,704 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 127 once invoked, about $0.0001 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-10-28.
Other skills, from other repositories
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
github
Complete guide for the GitHub plugin — REST API access for repositories, issues, pull requests, actions, releases, and search using a GitHub Personal Access Token.
ship-change
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…
akiship
Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION = the literal token /akiship, or an imperative turn, in any language, ordering the release ritual for this repo. A question about it, or a completion word with no release object, activates nothing — consult the checklist and…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.