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.
git 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/plugins/erraggy/oastools/plugin)<a href="https://agentmods.dev/plugins/erraggy/oastools/plugin"><img src="https://agentmods.dev/badge/plugins/erraggy/oastools/plugin/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/plugins/erraggy/oastools/plugin"><img src="https://agentmods.dev/badge/plugins/erraggy/oastools/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
oastools 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
{
"name": "oastools",
"description": "OpenAPI Specification tools — validate, fix, convert, diff, walk, and generate from OAS 2.0-3.2 documents",
"version": "1.66.0",
"author": {
"name": "erraggy",
"url": "https://github.com/erraggy"
},
"repository": "https://github.com/erraggy/oastools",
"license": "MIT",
"homepage": "https://erraggy.github.io/oastools/"
}
What it installs
The manifest is a name and a version. 5 skills, 1 hook travel with it, and installing the plugin installs all of them — 86 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 13 lines scan A d84c758d7049
oastools is a plugin published in the GitHub repository erraggy/oastools (6 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
cli-printing-press
Generate production Go CLIs from API descriptions or OpenAPI specs.
jwt
Development guide for the jwt JSON Web Token library for Go: signing and verifying tokens, claims and expiry, algorithm choice (HMAC/RSA/RSA-PSS/ECDSA/EdDSA), kid-based key rotation, JWKS fetch/refresh/publish, blocklisting and testing.
structpages
Patterns and guidance for the structpages Go web framework (struct-based routing + gsx + HTMX).
oas
Adaptive API code generator that learns your project patterns and syncs with OpenAPI specs.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.