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 toolsdk-ai/toolsdk-mcp-registry --skill check-mcp-jsongit clone --depth 1 https://github.com/toolsdk-ai/toolsdk-mcp-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/toolsdk-ai/toolsdk-mcp-registry/check-mcp-json)<a href="https://agentmods.dev/skills/toolsdk-ai/toolsdk-mcp-registry/check-mcp-json"><img src="https://agentmods.dev/badge/skills/toolsdk-ai/toolsdk-mcp-registry/check-mcp-json/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/toolsdk-ai/toolsdk-mcp-registry/check-mcp-json"><img src="https://agentmods.dev/badge/skills/toolsdk-ai/toolsdk-mcp-registry/check-mcp-json.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.00068 | $0.01311 |
| Opus 5.5 | $0.00027 | $0.00524 |
| Sonnet 5.5 | $0.00014 | $0.00262 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
check-mcp-json 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 15d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check MCP JSON
Review registry contributions by validating their package JSON without installing, executing, or probing submitted MCP packages and services. The trusted registry validator is the merge gate.
Load Repository Rules
Read these files before acting:
AGENTS.mddocs/PR_REVIEW.mddocs/CONTRIBUTING.md
Repository instructions and the user's latest authorization override this skill.
Safety Boundaries
- Run the validator from a clean checkout whose
HEADequals the latest trusted base ref. - Never run scripts from a contributor branch.
- Never install or execute a submitted package. Do not run
make build,pnpm install, package lifecycle scripts, or a contributor-provided validation command. - Do not comment, close, edit, mark ready, or merge a PR until the user authorizes that action.
- Never use
--admin,--auto, or a merge method other than squash. - Review independent PRs in parallel. PRs with pairwise-disjoint changed paths and registry
identities may submit squash merges concurrently; retry GitHub's transient
Base branch was modifiedrejection after another merge lands. - Disable repository hooks for authorized commits and pushes with
-c core.hooksPath=/dev/null; hooks may run repository scripts unexpectedly.
Review Workflow
For a backlog, use node scripts/batch-registry-prs.mjs review from a clean, current trusted
main checkout. This uses the same validator rules and reads PR JSON through batched Git blobs;
it never checks out or runs contributor code. Review registry-review/report.md and official-source
links, then use node scripts/batch-registry-prs.mjs merge --approved "123 124" only for the PR
numbers explicitly authorized by the user. See docs/PR_REVIEW.md for CI gates, held submissions,
the manual workflow, and merge results. Keep the individual helper below for focused inspection.
-
Refresh the trusted checkout:
git switch main git fetch origin main git pull --ff-only origin main
What ships with it
3 files 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.
- 15d ago Changed · +9 lines 1ef9a606287e
- 18d ago Changed · +7 lines d5a5561ef0f6
- 1mo ago First seen · 115 lines · 68 tokens per session scan A fa52a5446120
check-mcp-json is a skill published in the GitHub repository toolsdk-ai/toolsdk-mcp-registry (202 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,311 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
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
review-work
Quality gate: verify each acceptance criterion of a completed task/work unit, run quality checks, and create follow-up tasks for gaps. Use before merging or to audit delivered work. Invoked as /agiflow:review-work . Uses getworkunit, gettask, updatetask, createtask, createtaskcomment.
cross-model-review
A second-opinion code review that asks a different AI model to independently inspect a change, then compares both reviews. It focuses on logic, security, consistency, and omissions.
ontoly-software-graph
Use Ontoly Software Graph evidence, CLI reports, MCP, and official Ontoly Agent Skills before searching source files when reviewing architecture, dependencies, request flows, configuration, impact, or security-sensitive ownership.
codegraph
A local code-graph query tool for an existing project. It maps symbols and their relationships so you can search for definitions, callers, callees, affected files, and focused context.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.