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/corpus-testnpx skills add erraggy/oastools --skill corpus-testgit 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.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.00024 | $0.00455 |
| Opus 5 | $0.00012 | $0.00228 |
| Sonnet 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 4d 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.
- 4d ago First seen · 81 lines · 24 tokens per session scan A 703f329bb93d
corpus-test is a skill published in the GitHub repository erraggy/oastools (5 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 455 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.