jentic-api-scorecard

A coding-agent add-on for checking OpenAPI documents against the Jentic API AI Readiness Framework. OpenAPI is a standard format for describing how a web API works.

In plain words
What is it for?
Use it to score and lint an OpenAPI document, improve its descriptions, create a reusable OpenAPI Overlay, and assess whether proposed changes break existing API behavior.
Why use it?
It helps reveal how well an API description can be understood and used by AI systems, instead of relying on an informal manual review. It can also guide improvements and check for breaking changes.

Plugin for Claude Code

Install

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.

agentmods
npx agentmods add plugins/jentic/jentic-api-scorecard/marketplace
Claude Code
/plugin marketplace add jentic/jentic-api-scorecard
Clone the repo
git clone --depth 1 https://github.com/jentic/jentic-api-scorecard

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

jentic-api-scorecard 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.

.claude-plugin/marketplace.json · 26 lines

What it actually says

{
  "name": "jentic-api-scorecard",
  "owner": {
    "name": "Jentic",
    "email": "[email protected]"
  },
  "description": "Agent skill for scoring OpenAPI documents against the Jentic API AI Readiness Framework (JAIRF).",
  "plugins": [
    {
      "name": "api-scorecard",
      "description": "Teaches coding agents to use the @jentic/api-scorecard-cli to score, lint, and assess the AI-readiness of an OpenAPI document.",
      "source": "./",
      "strict": false,
      "skills": ["./skills/jentic-api-scorecard"]
    },
    {
      "name": "api-improve",
      "description": "Teaches coding agents to raise an OpenAPI document's JAIRF score, producing an improved spec and a reusable OpenAPI Overlay. Improvements are non-breaking by default, with summary-description and full (breaking-allowed) modes and an oasdiff breaking-change check.",
      "source": "./",
      "strict": false,
      "skills": ["./skills/jentic-api-improve"],
      "agents": ["./agents/jentic-api-improve.md"]
    }
  ]
}
Changes

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.

  1. yesterday First seen · 26 lines scan A 448d52a33bef

Subscribe to this mod's changes

jentic-api-scorecard is a plugin published in the GitHub repository jentic/jentic-api-scorecard (21 stars, last pushed 7d ago), 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-08-30.