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/api-contract-keepergit clone --depth 1 https://github.com/sigistry/marketplaceGrade A, and why
api-contract-keeper 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 2d 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.
What it actually says
{
"name": "api-contract-keeper",
"version": "1.0.0",
"description": "Keeps your API and its spec in sync: detects and fixes OpenAPI/GraphQL spec-vs-code drift, hardens endpoints with request validation, RFC 9457 error envelopes and idempotency, guards against breaking changes, and audits job-queue reliability.",
"author": {
"name": "Sigistry API Contract Keeper",
"url": "https://github.com/Sigistry/marketplace/tree/main/plugins/api-contract-keeper"
},
"license": "MIT"
}
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.
- 2d ago First seen · 11 lines scan A 65e7086ffcf9
api-contract-keeper is a plugin published in the GitHub repository sigistry/marketplace (3 stars, last pushed 3d ago), 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-08-31.
Other plugins, from other repositories
netresearch-claude-code-marketplace
Curated Agentic Skills for AI coding agents — TYPO3, PHP, Go, Docker, Jira, security, and more. Platform-agnostic skills following the open Agent Skills specification.
overheid-plugins marketplace
Plugin marketplace listing 7 plugins: standaarden, zad-actions, developer-overheid, nerds, internet.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
handbook-qa
Browser automation and QA testing tools with Playwright MCP integration.
claude-ops
Claude Code operations toolkit. Twelve skills: audit-skill-visibility (audit whether each installed skill is actually VISIBLE to the model, and diagnose why most of a fleet never gets used — a skill is invisible when its description is dropped by Claude Code's skill-listing context budget, which sheds descriptions…
computer-use
Operating knowledge for Claude Code's built-in computer-use MCP server — the desktop screen-control surface. /computer-use:diagnose resolves a symptom to a cause instead of retrying: why every screenshot is downscaled to a fixed pixel budget and why zoom (not a bigger display) is the way back to detail, how to read a.