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/HermeticOrmus/LibreUIUX-Claude-CodeWrote 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/hermeticormus/libreuiux-claude-code/git-pr-workflows)<a href="https://agentmods.dev/plugins/hermeticormus/libreuiux-claude-code/git-pr-workflows"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreuiux-claude-code/git-pr-workflows/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/hermeticormus/libreuiux-claude-code/git-pr-workflows"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreuiux-claude-code/git-pr-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
git-pr-workflows 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 19d 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": "git-pr-workflows",
"version": "1.2.1",
"description": "Git workflow automation, pull request enhancement, and team onboarding processes",
"author": {
"name": "Seth Hobson",
"url": "https://github.com/wshobson"
},
"homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code",
"repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code",
"license": "MIT",
"keywords": [
"git",
"pull-request",
"workflow",
"onboarding",
"essential"
]
}
What it installs
The manifest is a name and a version. 2 commands travel with it, and installing the plugin installs all of them — 25 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · -10 lines e1fce927a12d
- 1mo ago First seen · 30 lines scan A 5d713f20a1b8
git-pr-workflows is a plugin published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (115 stars, last pushed 15d 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-09-03.
Other plugins, from other repositories
delivery-suite
Publish the intended changes and verify what reached the remote repository or target environment.
code-contribution-analysis
Skills for analyzing GitHub pull requests and issues in depth. Fetches contribution data from GitHub and researches architectural context via chunkhound-integration. Standalone useful for code review, and designed to be consumable by Claude Agent SDK applications.
engineering-workflow-plugin
Skills for software engineering workflows: git operations, test fixing, code review, feature planning, and ensemble problem solving (generates multiple solutions in parallel and selects the best).
diffctx
Selects the minimum code an LLM needs to review a git diff.
forgedock
Autonomous AI development pipeline that uses GitHub as a structured knowledge graph for Claude Code agents. Adds /work-on, /review-pr, /quality-gate, /orchestrate, and 20+ pipeline commands.
review-gate
Native Claude Code AI code review + blocking pre-push gate on your Claude subscription. Isolated headless reviewer, severity/confidence verdicts, fails closed. open-code-review, done compliantly.