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.
/plugin marketplace add skrrt-sh/skillsnpx agentmods add plugins/skrrt-sh/skills/shipgit clone --depth 1 https://github.com/skrrt-sh/skillsGrade A, and why
ship 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 3d 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": "ship",
"version": "5.0.0",
"description": "Git shipping workflow — conventional commits with gitmojis, PRs and MRs with the matching forge CLI, curated releases.",
"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"
],
"skills": [
"./commit",
"./pr",
"./release",
"./setup"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 139 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 28 lines scan A 116acad129d0
ship is a plugin published in the GitHub repository skrrt-sh/skills (2 stars, last pushed 27d 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
aidd-vcs
External artifacts: commit, pull-request, release-tag, issue-create.
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
contributor-writing
Writing skills for Shopware core contributors: Architecture Decision Records, PR descriptions (trunk and feature-branch formats), commit messages, and RELEASEINFO/UPGRADE entries. Analyzes branch diffs, classifies changes, and writes content calibrated to change magnitude.
stepwise-git
Git and GitHub workflow: semantic commits and rigorous PR comment review.
courier
A bundle of Claude Code skills that ship work already on disk: commit-changes-to-git stages only what the user named and writes one Conventional Commits message without pushing, and submit-a-pull-request pushes the current branch, opens a pull request with a short prose body explaining what changed and why, and pings…
workflow
Developer-workflow commands and skills — sandbox-safe Conventional commits with a commit.sh handoff, immutable code-scanning triage reports with SHA-pinned permalinks, and generation of evolve evaluation suites (triggers + behavioral evals) for agent skills.