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/docs)<a href="https://agentmods.dev/plugins/skrrt-sh/skills/docs"><img src="https://agentmods.dev/badge/plugins/skrrt-sh/skills/docs/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/docs"><img src="https://agentmods.dev/badge/plugins/skrrt-sh/skills/docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
docs 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": "docs",
"version": "3.0.0",
"description": "Documentation authoring — structured markdown with YAML frontmatter, Mermaid diagrams, and auto-fixed lint-clean output.",
"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": [
"markdown",
"documentation",
"mermaid",
"knowledge-base",
"markdownlint"
],
"skills": [
"./md-writer"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 67 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 First seen · 23 lines scan A 5ce2cf249d9c
docs 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
handbook-visual-explainer
Generate beautiful HTML pages for diagrams, diff reviews, plan reviews, slides, and data tables.
researcher
Create distinctive HTML one-pagers with curated aesthetics, converts to PDF.
office-plugin
Office document generation — professional PowerPoint presentations, polished Word documents, and Excel spreadsheets.
ai-prompt-guide
Intelligent document management and agent orchestration workflows for AI-assisted development.
deck-kit
Branded presentation deck toolkit. Ships three skills: deck-brand-init (brand.yaml scaffolding), deck-create (conversational HTML deck authoring), and deck-publish (HTML to PDF or PPTX via Puppeteer + pptxgenjs, both pixel-perfect screenshot and fully-editable modes). Works in Claude Code and GitHub Copilot CLI.
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…