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/anilcancakir/claude-code-pluginsWrote 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/anilcancakir/claude-code-plugins/pre-commit-flow)<a href="https://agentmods.dev/plugins/anilcancakir/claude-code-plugins/pre-commit-flow"><img src="https://agentmods.dev/badge/plugins/anilcancakir/claude-code-plugins/pre-commit-flow/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/anilcancakir/claude-code-plugins/pre-commit-flow"><img src="https://agentmods.dev/badge/plugins/anilcancakir/claude-code-plugins/pre-commit-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pre-commit-flow 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 1mo 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": "pre-commit-flow",
"version": "1.0.0",
"description": "Pre-commit quality assurance workflow with code review, documentation updates, and smart commits. Supports Laravel, Flutter, Vue 2/3, TailwindCSS, and Alpine.js.",
"author": {
"name": "Anilcan Cakir",
"email": "[email protected]"
},
"homepage": "https://github.com/anilcancakir/claude-code-plugins",
"repository": "https://github.com/anilcancakir/claude-code-plugins",
"license": "MIT",
"keywords": [
"pre-commit",
"code-review",
"documentation",
"commit-workflow",
"laravel",
"flutter",
"vue",
"quality-assurance"
],
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 3 skills, 4 commands, 3 agents travel with it, and installing the plugin installs all of them — 305 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill commit-changes A 24 tokens
- Skill review-changes A 30 tokens
- Skill update-docs A 24 tokens
- Command my_commit A 29 tokens
- Command my_send A 18 tokens
- Command my_docs A 14 tokens
- Command my_review A 20 tokens
- Agent code-reviewer A 64 tokens
- Agent doc-updater A 47 tokens
- Agent test-checker A 35 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.
- 1mo ago First seen · 24 lines scan A 5ec70484dc4f
pre-commit-flow is a plugin published in the GitHub repository anilcancakir/claude-code-plugins (6 stars, last pushed 8mo 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-31.
Other plugins, from other repositories
github
Skills for GitHub pull request workflows — creating PRs, addressing review feedback, and resolving threads.
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.
manifest-dev-tools
Tools for prompts and PRs alongside the manifest workflow. Includes collaborative PR walkthroughs, autonomous PR review that independently re-verifies a manifest gate by gate, author-side PR babysitting that drives the lifecycle toward green and mergeable, gap-calibrated prompt engineering, standalone goals distilled…
pull-request
Pull request workflows: create, update, babysit CI, and reviewer follow-up.
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
misuzu
Respond to PR review comments semi-automatically. Splits review findings into logical units, fixes and commits them one by one, then replies and resolves review threads.