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/Open-Agent-Tools/General-OAT-SkillsWrote 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/open-agent-tools/general-oat-skills/oat-check)<a href="https://agentmods.dev/plugins/open-agent-tools/general-oat-skills/oat-check"><img src="https://agentmods.dev/badge/plugins/open-agent-tools/general-oat-skills/oat-check/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/open-agent-tools/general-oat-skills/oat-check"><img src="https://agentmods.dev/badge/plugins/open-agent-tools/general-oat-skills/oat-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
oat-check 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 25d 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": "oat-check",
"version": "3.0.0",
"description": "Quick project health check: git status, recent commits, GitHub Actions, package build",
"author": {
"name": "Open Agent Tools"
},
"repository": "https://github.com/Open-Agent-Tools/General-OAT-Skills",
"license": "Apache-2.0",
"keywords": [
"dev-workflow",
"health-check"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 46 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 25d ago Changed · +3 lines 40317fd98f29
- 29d ago First seen · 12 lines scan A 588a5f0c07e2
oat-check is a plugin published in the GitHub repository Open-Agent-Tools/General-OAT-Skills (3 stars, last pushed 26d ago), licensed Apache-2.0. 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-09-17.
Other plugins, from other repositories
duet
Claude Code plugin for reflection, code quality, writing, and design.
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
foliowiki
Connect Claude Code to a Folio wiki over MCP: search, read and update pages, tables and whiteboards, with a skill that explains how.
mac-agent-hygiene
Keeps a Mac that runs Claude Code agents from filling its disk: a daily LaunchAgent plus an MCP server that clears regenerable caches (Xcode DerivedData, leftover plugin clones, browser-profile caches) and reaps stale git worktrees that are clean and already pushed. Plan first, apply on confirm.
release-please-monorepo
Set up automated semantic versioning, changelogs, and per-package publishing in a pnpm/Turbo monorepo using googleapis/release-please-action v4.
vibe-extras
Standalone utilities for codebase exploration, web research, git operations, and code maintenance.