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/yschimke/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/yschimke/skills/compose-review-skills)<a href="https://agentmods.dev/plugins/yschimke/skills/compose-review-skills"><img src="https://agentmods.dev/badge/plugins/yschimke/skills/compose-review-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/yschimke/skills/compose-review-skills"><img src="https://agentmods.dev/badge/plugins/yschimke/skills/compose-review-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
compose-review-skills 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 4d 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": "compose-review-skills",
"description": "Review Compose UI pull requests, set up preview CI, and check design parity.",
"version": "0.1.12",
"author": {
"name": "Yuri Schimke",
"url": "https://github.com/yschimke"
},
"repository": "https://github.com/yschimke/skills",
"license": "Apache-2.0"
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 364 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.
- 4d ago Changed 46a6dfe53d38
- 5d ago Changed b5e2eed2d420
- 10d ago Changed 0d675d288e7b
- 13d ago First seen · 12 lines scan A 69413b865d9d
compose-review-skills is a plugin published in the GitHub repository yschimke/skills (2 stars, last pushed 2d ago), 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-10-03.
Other plugins, from other repositories
praxis
Development workflow -- issue planning, implementation, PR creation, code review with specialized reviewers, and project conventions.
han-research
Pre-planning knowledge-work skills for the Han suite: understanding a problem before anyone commits to a plan. Home of research (research an open-ended question and end at an adversarially-validated recommendation), gap-analysis (compare two artifacts and report what is missing, incomplete, or conflicting), and…
human-state-skills
Response modes for overload, fog, plan stress-testing, and AI reality-checking.
notabene
Turnkey docs review: set up notabene on any repo — write the config, create the .notabene store, and start the review server via npx (no toolchain to install) — then run the human↔agent loop: process browser comments on your docs, apply the feedback, mark resolved, write the journal, and verify.
android-reverse-engineering
Decompile Android APK/JAR/AAR with jadx, trace call flows through libraries, and document extracted APIs.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.