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 agentmods add skills/luuow/meridian-mcp/api-referencenpx skills add LuuOW/meridian-mcp --skill api-referencegit clone --depth 1 https://github.com/LuuOW/meridian-mcpWrote 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/luuow/meridian-mcp/api-reference)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/api-reference"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/api-reference.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.02762 |
| Opus 5 | $0.00019 | $0.01381 |
| Sonnet 5 | $0.00008 | $0.00552 |
| Haiku 4.5 | $0.00004 | $0.00276 |
Grade A, and why
api-reference 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 3d 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 — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
api-reference
Production patterns for writing, validating, and publishing machine-readable API reference documentation. Covers OpenAPI 3.1, AsyncAPI 2.x, doc generation from code annotations, and consumer-facing reference portals.
OpenAPI 3.1 Document Skeleton
Start from a valid skeleton; fill in the gaps rather than building from scratch.
# openapi.yaml
openapi: "3.1.0"
info:
title: Acme API
version: "2.4.0"
description: |
REST API for the Acme platform.
**Base URL:** `https://api.acme.io/v2`
**Auth:** Bearer token via `Authorization` header
**Rate limits:** 1000 req/min per token
contact:
name: Platform Team
email: [email protected]
url: https://status.acme.io
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0
servers:
- url: https://api.acme.io/v2
description: Production
- url: https://sandbox.acme.io/v2
description: Sandbox (no billing, safe to test)
tags:
- name: widgets
description: Create and manage widgets
- name: auth
description: Authentication and token management
paths:
/widgets:
get:
operationId: listWidgets
tags: [widgets]
summary: List all widgets
description: |
Returns a paginated list of widgets owned by the authenticated account.
Results are sorted by `created_at` descending.
parameters:
- $ref: "#/components/parameters/PageParam"
- $ref: "#/components/parameters/LimitParam"
- name: status
in: query
schema:
type: string
enum: [active, archived, draft]
description: Filter by widget status
responses:
"200":
description: Paginated list of widgets
content:
application/json:
schema:
$ref: "#/components/schemas/WidgetList"
examples:
default:
$ref: "#/components/examples/WidgetListExample"
"401":
$ref: "#/components/responses/Unauthorized"
"429":
$ref: "#/components/responses/RateLimited"
components:
parameters:
PageParam:
name: page
in: query
schema:
type: integer
minimum: 1
default: 1
LimitParam:
name: limit
in: query
schema:
type: integer
minimum: 1
maximum: 100
default: 20
responses:
Unauthorized:
description: Missing or invalid authentication token
content:
application/json:
schema:
$ref: "#/components/schemas/Error"
example:
code: UNAUTHORIZED
message: "Bearer token is missing or expired"
RateLimited:
description: Rate limit exceeded
headers:
Retry-After:
schema:
type: integer
description: Seconds until the rate limit resets
content:
application/json:
schema:
$ref: "#/components/schemas/Error"
schemas:
Error:
type: object
required: [code, message]
properties:
code:
type: string
description: Machine-readable error code
example: VALIDATION_ERROR
message:
type: string
description: Human-readable error description
details:
type: array
items:
type: object
properties:
field:
type: string
issue:
type: string
securitySchemes:
BearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
security:
- BearerAuth: []
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.
- 3d ago First seen · 402 lines · 38 tokens per session scan A fb89f374049f
api-reference is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 2,762 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
api-docs-generator
Generate API documentation from code - produce OpenAPI/Swagger specs, Markdown API references, request/response examples, and interactive documentation from source code analysis.
openapi-glossary
Use consistent OpenAPI terminology and definitions when writing documentation, educational material, and tooling guidance.
scalar-docs
Skill for writing and updating scalar.config.json — Scalar Docs configuration reference for users and LLMs.
scalar-design-system
Scalar's design system — design tokens, theming (@scalar/themes), CSS variables, and the @scalar/components library. Use when designing or implementing Scalar UI, especially with Paper (code-to-design / design-to-code), so output matches real Scalar tokens, colors, typography, spacing, and components instead of…
cloud-agents-starter
Minimal starter runbook for cloud agents to install dependencies, run packages, execute tests, and troubleshoot the Scalar monorepo quickly.
mock-server
Build, customize, and troubleshoot OpenAPI mock servers with @scalar/mock-server, including x-handler, x-seed, authentication, and Docker.