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 dkmqflx/git-workflow-pluginnpx agentmods add plugins/dkmqflx/git-workflow-plugin/marketplacegit clone --depth 1 https://github.com/dkmqflx/git-workflow-pluginGrade A, and why
git-workflow-plugin 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-workflow-plugin",
"description": "Git branch/worktree lifecycle skills for Claude Code",
"owner": {
"name": "dkmqflx",
"email": "[email protected]"
},
"plugins": [
{
"name": "git-workflow",
"source": "./plugins/git-workflow",
"description": "5 git workflow skills covering worktree/branch creation (from the current position or a named base branch), opening PRs with an AI-drafted title/body, and cleaning up branches/worktrees after merge."
}
]
}
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 · 16 lines scan A 1d2f5eb5bdff
git-workflow-plugin is a plugin published in the GitHub repository dkmqflx/git-workflow-plugin (1 stars, last pushed 1mo 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
marketplace
Plugin marketplace listing 9 plugins: dev-tools, general, design, office-automation, business.
nestjs-best-practices-plugin
NestJS best-practice skills for Claude Code.
nestjs-best-practices
12 NestJS best-practice skills (90 rules) covering modules & DI, controllers, validation, guards/auth, interceptors, exception filters, config, database, caching/queues, testing, security, and performance/logging.
ainb-hooks
Emit every safely observable Claude Code lifecycle event into Hangar's durable provider log. User-facing events still reach ainb-notifyd over its Unix socket. The same notify.sh powers ATC structured control when installed with AINBMANAGED=atc. stallguard.py additionally blocks turn-end when a session would idle on i.
onebrain
OneBrain — Your AI Thinking Partner.
ai-maestro-plugins
Plugin marketplace listing 1 plugin: ai-maestro.