Borrowing it
Nothing to install: this file belongs to erraggy/oastools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/erraggy/oastools/main/.claude/skills/corpus-test/SKILL.mdgit clone --depth 1 https://github.com/erraggy/oastoolsWrote 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/erraggy/oastools/corpus-test)<a href="https://agentmods.dev/skills/erraggy/oastools/corpus-test"><img src="https://agentmods.dev/badge/skills/erraggy/oastools/corpus-test/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/erraggy/oastools/corpus-test"><img src="https://agentmods.dev/badge/skills/erraggy/oastools/corpus-test.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.00024 | $0.00455 |
| Opus 5.5 | $0.00010 | $0.00182 |
| Sonnet 5.5 | $0.00005 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
corpus-test 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 1mo 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
corpus-test
Run integration tests against the corpus of real-world OpenAPI specifications.
Usage:
/corpus-test— run all corpus tests/corpus-test short— exclude large specs (faster)
Step 1: Check Corpus Availability
Use the Glob tool to check for corpus files:
pattern: testdata/corpus/*.{json,yaml,yml}
If no corpus files found, download them:
make corpus-download
Step 2: Run Corpus Tests
Based on the mode argument:
Full mode (default):
make test-corpus
Short mode (argument = "short"):
make test-corpus-short
Capture and analyze the output.
Step 3: Analyze Results
Note: Corpus specs are real-world documents (Plaid, DigitalOcean, GitHub, etc.) that often contain validation errors intentionally. Validation failures are expected — the key metric is whether the fixer resolves them.
For each corpus spec, report:
- ✅ Parse/validate/fix succeeded
- ❌ Failures with error details (fixer failed to resolve validation errors)
- ⚠️ New warnings compared to expected behavior
Step 4: Report
## Corpus Test Results
| Spec | Parse | Validate | Fix | Notes |
|------|-------|----------|-----|-------|
| petstore.yaml | ✅ | ✅ | ✅ | |
| github-api.json | ✅ | ❌ | ⚠️ | [details] |
| ... | ... | ... | ... | ... |
### Summary
- **Passed**: N/M specs
- **Failed**: [list]
- **New issues**: [list]
Step 5: Offer Actions
If failures are found:
- Investigate — deep dive into specific failures
- Compare with main — check if failures are regressions
- File issues — create GitHub issues for new failures
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.
- 1mo ago First seen · 81 lines · 24 tokens per session scan A 703f329bb93d
corpus-test is a skill published in the GitHub repository erraggy/oastools (6 stars, last pushed 9d ago), licensed MIT. It adds 24 tokens to every session and 455 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
API Contract Validator
Validate API responses against OpenAPI/Swagger specifications, JSON Schema definitions, and consumer-driven contracts to prevent breaking changes.
fastapi-docs
FastAPI 0.115+ — path/query params, Pydantic, dependency injection, OAuth2/JWT, middleware, WebSocket, testing.
microcks-openapi-mocking
Write OpenAPI examples that work with Microcks dispatchers for API mocking. Covers example pairing rules, JSON body dispatching, Groovy script dispatching, and dispatcher configuration via the Microcks API.
microcks-import-artifacts
Import OpenAPI specifications into a running Microcks instance and auto-configure dispatchers based on vendor extensions. Provides shell script templates for importing specs, downloading microcks-cli, and setting up JSONBODY or SCRIPT dispatchers.
orval
Generate type-safe API clients, TanStack Query/SWR hooks, Zod schemas, MSW mocks, Hono server handlers, MCP servers, and SolidStart actions from OpenAPI specs using Orval. Covers all clients (React/Vue/Svelte/Solid/Angular Query, Fetch, Axios), custom HTTP mutators, authentication patterns, NDJSON streaming…