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/Jamie-BitFlight/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/jamie-bitflight/claude_skills/commitlint)<a href="https://agentmods.dev/plugins/jamie-bitflight/claude_skills/commitlint"><img src="https://agentmods.dev/badge/plugins/jamie-bitflight/claude_skills/commitlint.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
commitlint 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": "commitlint",
"description": "When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.",
"version": "1.1.10",
"author": {
"name": "Jamie Nelson",
"url": "https://github.com/bitflight-devops"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 54 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 First seen · 10 lines scan A 7f40068ffce9
commitlint is a plugin published in the GitHub repository Jamie-BitFlight/claude_skills (65 stars, last pushed yesterday), 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-03.
Other plugins, from other repositories
git-pr
Committing, PR creation and review triage, and dependency upgrades.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
cas
Evidence-driven research, guarded Codex delegation, explicit native parallelism, secret protection, and approval gates for rm, commit, and push.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
matt-pocock-skills
Bundled non-deprecated skills from Matt Pocock's Skills For Real Engineers (https://github.com/mattpocock/skills): engineering skills plus caveman, handoff, write-a-skill, git-guardrails-claude-code, and setup-pre-commit.
prek
Set up git pre-commit hooks with prek, the fast pre-commit-compatible runner.