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/skrrt-sh/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/skrrt-sh/skills/skills)<a href="https://agentmods.dev/plugins/skrrt-sh/skills/skills"><img src="https://agentmods.dev/badge/plugins/skrrt-sh/skills/skills/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/skrrt-sh/skills/skills"><img src="https://agentmods.dev/badge/plugins/skrrt-sh/skills/skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
skrrt 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": "skrrt",
"version": "6.2.0",
"description": "Every skrrt skill in one bundle for the skills.sh CLI — git shipping workflow, structured markdown authoring with auto-fixed lint-clean output, subagent orchestration, and self-documenting code discipline. Claude Code installs per bucket instead; see marketplace.json.",
"author": {
"name": "skrrt-sh",
"url": "https://github.com/skrrt-sh"
},
"homepage": "https://github.com/skrrt-sh/skills",
"repository": "https://github.com/skrrt-sh/skills",
"license": "MIT",
"keywords": [
"git",
"conventional-commits",
"gitmoji",
"pull-requests",
"merge-requests",
"releases",
"changelog",
"markdown",
"subagents",
"comments",
"documentation"
],
"skills": [
"./skills/ship/commit",
"./skills/ship/pr",
"./skills/ship/release",
"./skills/ship/setup",
"./skills/docs/md-writer",
"./skills/dev/subagents",
"./skills/dev/self-documenting"
]
}
What it installs
The manifest is a name and a version. 3 plugins travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago Changed · +3 lines 1dbe755534d9
- 1mo ago Changed · +2 lines 79d98e513dfc
- 1mo ago First seen · 30 lines scan A 0742bb485b08
skrrt is a plugin published in the GitHub repository skrrt-sh/skills (2 stars, last pushed 1mo 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
release-conductor
Owns everything around the diff: craft Conventional Commits and PR descriptions, recommend the right semver bump by reasoning about behavioral breaking changes, assemble changelogs from messy history, and guide merge-conflict resolution, rebase planning, and git-history archaeology.
github
GitHub CLI, stacked PRs, Actions docs, and issue management skills.
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read — filtered to what they'd notice, one theme, one bullet per idea, no code vocabulary.
claude-plugin-repo-ci-release
Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (one with a .claude-plugin/marketplace.json and plugins/). Adds two GitHub Actions — a structure validator on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever VERSION changes — plus the.
open-source
Collection of skills for open-source R and Python package developers.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.