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/dev)<a href="https://agentmods.dev/plugins/skrrt-sh/skills/dev"><img src="https://agentmods.dev/badge/plugins/skrrt-sh/skills/dev/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/dev"><img src="https://agentmods.dev/badge/plugins/skrrt-sh/skills/dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dev 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": "dev",
"version": "1.1.0",
"description": "Implementation workflow — orchestrate strictly scoped subagents from a reviewing main thread, and keep the code the single source of truth with why-only comments and decision-only docs.",
"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": [
"subagents",
"orchestration",
"parallel",
"delegation",
"code-review",
"comments",
"documentation",
"claude-md"
],
"skills": [
"./subagents",
"./self-documenting"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 194 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.
- 1mo ago Changed · +4 lines 1ccfd8837f52
- 1mo ago First seen · 23 lines scan A 18896896c7e4
dev 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-09-05.
Other plugins, from other repositories
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…
handbook-code-review
Code review plugin with a standalone reviewer agent and two skill strategies: disposable subagents for one-shot reviews and persistent team members for iterative reviews.
sigistry marketplace
Discover plugins that supercharge your Claude Code workflow with advanced security, architecture, and performance insights.
python-dev
Python development workflow with architecture design, coding guidelines, testing patterns, and specialized review agents.
review-pr
Review PRs in a Tour Guide (expository) or Adversarial (audit) posture, with logical file ordering, context, and severity-rated findings. Forge-agnostic (GitHub + Bitbucket).
code-auditor
Comprehensive code auditing plugin with parallel security, quality, architecture, performance, and testing agents powered by reusable assessment skills.