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/erraggy/oastools/validate-specnpx skills add erraggy/oastools --skill validate-specgit clone --depth 1 https://github.com/erraggy/oastoolsWhat 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.00018 | $0.00614 |
| Opus 5 | $0.00009 | $0.00307 |
| Sonnet 5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
validate-spec 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate an OpenAPI Specification
Step 1: Run validation
Call the validate tool on the user's spec:
{"spec": {"file": "<path>"}}
If the user wants strict validation, add "strict": true.
⚠️ Tip for large specs: Use "no_warnings": true for initial triage. Large specs can produce hundreds of warnings that obscure the actual errors. Get the error picture first, then run again without no_warnings to review warnings separately.
Step 2: Report results
If the spec is valid:
- Confirm it passes validation
- Mention the detected OAS version
- Note any warnings (unless
no_warningswas set)
If the spec has errors:
- List each error with its JSON path and a plain-language explanation
- Group related errors (e.g., multiple missing
$reftargets) - Explain why each error matters and what it would cause in practice (tooling failures, code generation issues, etc.)
Paginating large results
Results are paginated (default limit: 100). When returned < error_count, there are more errors:
{"spec": {"file": "<path>"}, "offset": 100, "limit": 100}
⚠️ Strategy for large error sets: Analyze the first page for patterns — if errors are repetitive (e.g., hundreds of missing path parameters), summarize the pattern and total count rather than paging through all of them. Only page further when errors appear diverse or the user needs specifics.
Step 3: Suggest fixes
For each error, explain how to fix it. Common patterns:
| Error type | Suggested fix |
|---|---|
| Missing path parameter | Add the parameter to the operation's parameters array |
| Duplicate operationId | Rename to be unique, following a verb+resource pattern |
Invalid $ref target |
Fix the reference path, or stub the missing schema |
| Missing required field | Add the field with an appropriate value |
If the errors are auto-fixable, offer to run the fix tool:
{"spec": {"file": "<path>"}, "dry_run": true}
Show the user the planned fixes before applying. ✅ When applying, use output to persist:
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 · 78 lines · 18 tokens per session scan A 7e0f3e0da997
validate-spec is a skill published in the GitHub repository erraggy/oastools (5 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 614 once invoked, about $0.0001 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
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.
tests
Write clear, maintainable Vitest and Playwright tests with precise assertions, consistent structure, and strong behavioral coverage.