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/barnburner121/claude-plugin-marketplaceWrote 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/barnburner121/claude-plugin-marketplace/commit-linter)<a href="https://agentmods.dev/plugins/barnburner121/claude-plugin-marketplace/commit-linter"><img src="https://agentmods.dev/badge/plugins/barnburner121/claude-plugin-marketplace/commit-linter.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
commit-linter 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 3d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 10 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.
- 3d ago First seen · 2 lines scan A 92c35fc185a5
commit-linter is a plugin published in the GitHub repository barnburner121/claude-plugin-marketplace (3 stars, last pushed 5mo 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-03.
Other plugins, from other repositories
git-town-workflow
Prescriptive git-town workflow enforcement for fork-based development: fork creation, contribution workflow, enforcement hooks that block forbidden raw git commands.
git
Version-control skills for the whole branch lifecycle: committing, worktrees, merge conflicts, undo/recovery, PR descriptions, changelogs, releases, and branch cleanup.
dev-loop
The everyday dev loop as three stack-neutral commands: fix debugs a bug or batch-applies a review report by severity, commit runs pre-flight checks and drafts a conventional message behind a sensitive-file gate, ship chains review, fix, and commit with a gate between each phase.
codeops
Universal AI-development workflow: planning, requirements engineering, reverse-engineering, disambiguation, preflight audits, architecture docs, roadmaps, upgrades, and git commit flows. Ported from codeops-mcp.
ai-stack
Useful AI things an engineer uses daily. Ships prodcheck (senior-engineer production review), prodtest (senior-QA test pass with Playwright), mergemain (context-aware merge of main into the current branch), and shipit (clean commits and PRs, with or without AI attribution).
commit
Creates git commits using conventional commit format with appropriate emojis, following project standards and creating descriptive messages that explain the purpose of changes.