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.
/plugin marketplace add rohitg00/awesome-claude-code-toolkitnpx agentmods add plugins/rohitg00/awesome-claude-code-toolkit/git-flowgit clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkitWrote 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/rohitg00/awesome-claude-code-toolkit/git-flow)<a href="https://agentmods.dev/plugins/rohitg00/awesome-claude-code-toolkit/git-flow"><img src="https://agentmods.dev/badge/plugins/rohitg00/awesome-claude-code-toolkit/git-flow.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
git-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 yesterday.
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": "git-flow",
"version": "1.0.0",
"description": "Git workflow management with feature branches, releases, and hotfix flows",
"commands": ["commands/flow-start.md", "commands/flow-release.md"]
}
What it installs
The manifest is a name and a version. 2 commands travel with it, and installing the plugin installs all of them — 0 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.
- yesterday First seen · 7 lines scan A 91237de6ba05
git-flow is a plugin published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,585 stars, last pushed 3mo ago), licensed Apache-2.0. 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
adaptive-communication
Detects user communication style (high-context relational vs low-context transactional) and adapts responses accordingly.
bmad-skills
BMAD Skills collection for Claude Code.
obshare-cli
Upload Obsidian Markdown documents to Feishu (Lark) cloud documents. Skills for environment setup, configuration, direct-share plugin workflows, uploading notes, managing permissions, and viewing upload history.
capstone
仕上げ・記録・公開を通じて，プロジェクトを完成という頂へ載せきる工程スキル群．.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.