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/Borda/AI-RigWrote 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/borda/ai-rig/cc_oss)<a href="https://agentmods.dev/plugins/borda/ai-rig/cc_oss"><img src="https://agentmods.dev/badge/plugins/borda/ai-rig/cc_oss/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/borda/ai-rig/cc_oss"><img src="https://agentmods.dev/badge/plugins/borda/ai-rig/cc_oss.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
oss 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 today.
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
{
"author": {
"name": "Jirka",
"url": "https://github.com/Borda/AI-Rig"
},
"description": "Open-source maintenance: analyse, review, resolve, release-readiness, and setup skills with four specialist agents",
"keywords": [
"oss",
"github",
"ci",
"release",
"review",
"maintenance"
],
"license": "Apache-2.0",
"name": "oss",
"repository": "https://github.com/Borda/AI-Rig",
"version": "0.50.2"
}
What it installs
The manifest is a name and a version. 3 skills, 4 agents travel with it, and installing the plugin installs all of them — 1,147 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.
- today Changed e52493a0a910
- yesterday Changed b9fd6e1b4283
- 2d ago Changed 3fe7422528ca
- 4d ago Changed ba294b1f0cbd
- 5d ago Changed a559412fcf38
- 6d ago Changed 04700674cda9
- 10d ago Changed f709fda4a402
- 11d ago Changed b1fc006e9ccb
- 12d ago Changed ebd994a794bb
- 13d ago First seen · 20 lines scan A adca23dbb0a7
oss is a plugin published in the GitHub repository Borda/AI-Rig (28 stars, last pushed today), 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-30.
Other plugins, from other repositories
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.
fuse-commit-pro
Professional git commits with Conventional Commits, GitHub Flow branch enforcement, auto PR creation, security validation, and auto-detection.
fuse-ai-pilot
AI Pilot workflow agents: sniper (code quality), research-expert, explore-codebase, websearch.
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.