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/Microck/ordinary-claude-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/microck/ordinary-claude-skills/claude-win11-speckit-update-skill)<a href="https://agentmods.dev/plugins/microck/ordinary-claude-skills/claude-win11-speckit-update-skill"><img src="https://agentmods.dev/badge/plugins/microck/ordinary-claude-skills/claude-win11-speckit-update-skill/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/microck/ordinary-claude-skills/claude-win11-speckit-update-skill"><img src="https://agentmods.dev/badge/plugins/microck/ordinary-claude-skills/claude-win11-speckit-update-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
speckit-updater 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What it installs
The manifest is a name and a version. 2 skills, 8 commands travel with it, and installing the plugin installs all of them — 146 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill claude-win11-speckit-update-skill A 0 tokens
- Skill speckit-updater A 0 tokens
- Command speckit.checklist A 13 tokens
- Command speckit.clarify A 27 tokens
- Command speckit.specify A 13 tokens
- Command speckit.analyze A 26 tokens
- Command speckit.implement A 14 tokens
- Command speckit.tasks A 18 tokens
- Command speckit.constitution A 21 tokens
- Command speckit.plan A 14 tokens
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.
- 5d ago First seen · 30 lines scan A 45d96a686d5a
speckit-updater is a plugin published in the GitHub repository Microck/ordinary-claude-skills (394 stars, last pushed 5d ago), with no licence file. 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-07.
Other plugins, from other repositories
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
fuse-commit-pro
Professional git commits with Conventional Commits, GitHub Flow branch enforcement, auto PR creation, security validation, and auto-detection.
block-forbidden-git-add
Denies git commands that stage protected paths, whole-tree adds, or rewrite history.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
merge-pr
Merge PRs matching repo history conventions. Includes readiness checks, CI watching, stack detection, and automated rebasing.
research
Study dependencies locally. Clones upstream repos and creates version-pinned worktrees matching your project's exact versions.