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/the-open-agent/oss-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/the-open-agent/oss-skills/oss-skills)<a href="https://agentmods.dev/plugins/the-open-agent/oss-skills/oss-skills"><img src="https://agentmods.dev/badge/plugins/the-open-agent/oss-skills/oss-skills.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
oss-skills 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 7d 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": "oss-skills",
"description": "18 skills for open-source development: bootstrapping repos, API design, testing, CI, releases, supply-chain security, docs, triage, contributor experience, launch, and governance.",
"version": "0.1.0",
"homepage": "https://github.com/the-open-agent/oss-skills",
"repository": "https://github.com/the-open-agent/oss-skills",
"license": "Apache-2.0",
"keywords": [
"open-source",
"skills",
"claude-code",
"agent-skills",
"maintainer",
"github",
"ci",
"release-engineering",
"supply-chain-security",
"documentation"
]
}
What it installs
The manifest is a name and a version. 18 skills travel with it, and installing the plugin installs all of them — 1,937 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill governance-and-sustainability A 95 tokens
- Skill api-design A 107 tokens
- Skill code-review A 118 tokens
- Skill contributor-experience A 101 tokens
- Skill dependency-hygiene A 101 tokens
- Skill docs-architecture A 116 tokens
- Skill issue-triage A 102 tokens
- Skill launch-and-growth A 108 tokens
- Skill license-and-legal A 103 tokens
- Skill performance-benchmarking A 92 tokens
- Skill readme-that-converts A 117 tokens
- Skill refactor-safely A 109 tokens
- Skill release-engineering A 108 tokens
- Skill supply-chain-security A 100 tokens
- Skill testing-strategy A 114 tokens
- Skill open-source-playbook A 131 tokens
- Skill repo-bootstrap A 111 tokens
- Skill ci-pipelines B 104 tokens
What ships with it
1 file 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.
- 7d ago First seen · 21 lines scan A de72565f41e9
oss-skills is a plugin published in the GitHub repository the-open-agent/oss-skills (5 stars, last pushed 1mo 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-08-31.
Other plugins, from other repositories
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
aidd-vcs
External artifacts: repo-init, commit, pull-request, release-tag, issue-create.
aio-devops
GitHub, GitLab, and git worktree workflows in one toolkit — manage repos, PRs, MRs, pipelines, and parallel branches without juggling CLIs.
socket-release
Stand up SocketDev publishing (npm, crates.io, GitHub releases, Homebrew tap) in a repo: copy in the release kit and run its bootstrap - name reservation, GitHub environments, npm trusted publisher, staged publish config, verification.
release
Cut and bump releases with safe defaults (no automatic push/tag). Rolls out releases to downstream consumers with CI verification.
release-please-monorepo
Set up automated semantic versioning, changelogs, and per-package publishing in a pnpm/Turbo monorepo using googleapis/release-please-action v4.