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/coleam00/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/coleam00/skills/skills)<a href="https://agentmods.dev/plugins/coleam00/skills/skills"><img src="https://agentmods.dev/badge/plugins/coleam00/skills/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/coleam00/skills/skills"><img src="https://agentmods.dev/badge/plugins/coleam00/skills/skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 10d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "skills",
"displayName": "Cole's AI Skills",
"version": "1.4.5",
"description": "The PIV loop (plan, implement, validate, review, commit, PR) plus priming, planning, worktrees, and the meta-skills for building your own AI Layer.",
"author": {
"name": "Cole Medin",
"url": "https://github.com/coleam00"
},
"homepage": "https://github.com/coleam00/skills",
"repository": "https://github.com/coleam00/skills",
"license": "MIT",
"keywords": [
"piv-loop",
"planning",
"code-review",
"worktrees",
"ai-layer",
"agentic-coding"
],
"skills": ["./.claude/skills"]
}
What it installs
The manifest is a name and a version. 36 skills travel with it, and installing the plugin installs all of them — 3,410 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill piv-plan-implementation A 79 tokens
- Skill second-brain-audit A 144 tokens
- Skill hooks-create A 102 tokens
- Skill second-brain-fix A 109 tokens
- Skill build-signal-engine A 206 tokens
- Skill ablate-ai-layer A 179 tokens
- Skill ast-grep A 80 tokens
- Skill plan-architecture A 152 tokens
- Skill plan-create-prd A 108 tokens
- Skill piv-implement-issue A 59 tokens
- Skill piv-investigate-issue A 68 tokens
- Skill piv-slice-epic A 89 tokens
- Skill piv-review-pr A 80 tokens
- Skill system-evolution-review A 48 tokens
- Skill piv-create-pr A 67 tokens
- Skill piv-implement A 36 tokens
- Skill rules-check-drift A 90 tokens
- Skill worktree-create A 92 tokens
- Skill piv-review-changes A 43 tokens
- Skill piv-validate A 54 tokens
- Skill setup-ai-tutor A 68 tokens
- Skill rules-create-global A 133 tokens
- Skill opportunity-scan A 95 tokens
- Skill skills-create A 85 tokens
- Skill prime-backend A 76 tokens
- Skill plan-create-stories A 66 tokens
- Skill prime-codebase A 66 tokens
- Skill prime-frontend A 70 tokens
- Skill worktree-merge A 80 tokens
- Skill piv-fix-review-findings A 72 tokens
- Skill piv-run-full-loop A 48 tokens
- Skill system-execution-report A 43 tokens
- Skill piv-commit A 37 tokens
- Skill drive-screen C 167 tokens
- Skill build-dark-factory D 219 tokens
- Skill agent-browser A 200 tokens
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed 1d817170f93b
- 1mo ago Changed 11d76afb984e
- 1mo ago Changed 59cbe84155e6
- 1mo ago First seen · 24 lines scan A 2774f538591d
skills is a plugin published in the GitHub repository coleam00/skills (708 stars, last pushed 11d 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-30.
Other plugins, from other repositories
git-sidebar
A lazygit-style side pane: every worktree of the repository and its local branches as rows you click. A worktree row moves the session there with /cd; a branch row shows its last commits and offers switch (clean tree only) or open worktree. Docked floor to ceiling beside the transcript in the fullscreen layout, above…
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
digest
Summarize AI-generated branches, PRs, and diffs into icon-rich cards, explain code state with git archaeology as self-contained HTML explainers, plus multi-project weekly recall digests.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.