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 jschulte/claude-plugins --skill health-audit-apigit clone --depth 1 https://github.com/jschulte/claude-pluginsWrote 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/jschulte/claude-plugins/health-audit-api)<a href="https://agentmods.dev/skills/jschulte/claude-plugins/health-audit-api"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/health-audit-api/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/jschulte/claude-plugins/health-audit-api"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/health-audit-api.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.00112 | $0.08887 |
| Opus 5.5 | $0.00045 | $0.03555 |
| Sonnet 5.5 | $0.00022 | $0.01777 |
| Haiku 4.5 | $0.00011 | $0.00889 |
Grade A, and why
health-audit-api 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 24d 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 — 608 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Surface Quality Health Audit Skill
Use this skill when the user wants a deep audit of the quality of an API as experienced by its consumers — developers integrating with it. The skill may audit the full API surface or focus on a user-specified endpoint family, webhook system, auth surface, SDK layer, or contract concern. This is NOT a code quality, architecture, or internal maintainability audit. /health-audit does that. This skill is about the external contract: consistency, predictability, correctness, and developer experience of every programmatic interface exposed to consumers. Applies to REST APIs, GraphQL APIs, webhooks, SDKs, and any programmatic interface with defined contracts.
Mission
Perform a rigorous, evidence-backed audit of the API surface from the perspective of a developer integrating with it for the first time. Evaluate the consistency, correctness, predictability, and developer experience of the external contract across endpoint design, request/response shapes, error handling, versioning, authentication, pagination, rate limiting, idempotency, documentation, webhooks, performance signals, and SDK quality.
Calibrate the review to the actual API:
- What kind of API is this? (REST, GraphQL, gRPC, webhook system, SDK)
- Who are the consumers? (Third-party developers, internal teams, mobile clients, partner integrations)
- What is the API's maturity? (Prototype, private beta, public GA)
- Is this a single API or a suite of APIs across multiple services?
- Internal APIs between microservices count if they have defined contracts
Do not produce vague "API best practices" fluff. Do not invent problems. Do not opine on REST vs. GraphQL vs. RPC — audit the quality of whatever approach was chosen. Consistency matters more than any specific convention. If there is no external API (pure frontend app, no exposed endpoints), say so and skip.
Focus Prompt Support
This skill can take an optional prompt that describes the API area to focus on.
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.
- 24d ago First seen · 608 lines · 112 tokens per session scan A f30ca9b1de73
health-audit-api is a skill published in the GitHub repository jschulte/claude-plugins (0 stars, last pushed 25d ago), licensed MIT. It adds 112 tokens to every session and 8,887 once invoked, about $0.0004 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-12.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
ring:mapping-streaming-events
Mapping the eventable points in a Lerian Go service where lib-streaming should emit past-tense, durable, tenant-scoped business events, producing a PM-validated event catalog and instrumentation-map.json for ring:instrumenting-streaming-events. Three-pass discovery (Survey, Slice, Mark) with a scope fence and delivery…