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-publish-rust)<a href="https://agentmods.dev/plugins/open-agent-tools/general-oat-skills/oat-publish-rust"><img src="https://agentmods.dev/badge/plugins/open-agent-tools/general-oat-skills/oat-publish-rust/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-publish-rust"><img src="https://agentmods.dev/badge/plugins/open-agent-tools/general-oat-skills/oat-publish-rust.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
oat-publish-rust 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-publish-rust",
"version": "3.0.0",
"description": "Rust crate/workspace release: verification gates, version bump, signed tag, CI or direct crates.io publish",
"author": {
"name": "Open Agent Tools"
},
"repository": "https://github.com/Open-Agent-Tools/General-OAT-Skills",
"license": "Apache-2.0",
"keywords": [
"release",
"publishing",
"versioning",
"rust",
"cargo"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 33 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 a3aff7a937a1
- 29d ago First seen · 15 lines scan A e26d14343a90
oat-publish-rust 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
go-release
Release engineering for Go modules and applications — semantic versioning, breaking-change detection, deprecation conventions, go.mod hygiene, and binary distribution with GoReleaser.
sw
Portable intent and verified progress across coding tools. Eleven focused workflow skills, two default lifecycle hooks, and a deterministic CLI and live local dashboard.
utility-tools
Developer productivity tools for Claude Code — generate McKinsey-style HTML slide decks from marketing strategies, automate software releases with version bumping, changelog generation, git tagging, and GitHub release publishing. 3 skills for teams shipping fast.
aura-gemini
Aura Shell integration for Gemini CLI - native notifications and session status.
workflow
Git and GitHub workflow skills — commits, branches, pull requests, issues, and CI actions.
set-up-installers
Set up installer and distribution methods for Go, Swift, Rust and Zig projects, configure GoReleaser publishing, and write or update Homebrew formulae.