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 HermeticOrmus/LibreUIUX-Claude-Codenpx agentmods add plugins/hermeticormus/libreuiux-claude-code/cicd-automationgit 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/cicd-automation)<a href="https://agentmods.dev/plugins/hermeticormus/libreuiux-claude-code/cicd-automation"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreuiux-claude-code/cicd-automation.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cicd-automation 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": "cicd-automation",
"source": "./plugins/cicd-automation",
"description": "CI/CD pipeline configuration, GitHub Actions/GitLab CI workflow setup, and automated deployment pipeline orchestration",
"version": "1.2.1",
"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": [
"ci-cd",
"automation",
"pipeline",
"github-actions",
"gitlab-ci"
],
"category": "infrastructure",
"strict": false,
"commands": [
"./commands/workflow-automate.md"
],
"agents": [
"./agents/deployment-engineer.md",
"./agents/devops-troubleshooter.md",
"./agents/kubernetes-architect.md",
"./agents/cloud-architect.md",
"./agents/terraform-specialist.md"
],
"skills": [
"./skills/deployment-pipeline-design",
"./skills/github-actions-templates",
"./skills/gitlab-ci-patterns",
"./skills/secrets-management"
]
}What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 170 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 marketplace.json#cicd-automation 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.
- yesterday First seen · 38 lines scan A 6c025e2642d5
cicd-automation is a plugin published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (100 stars, last pushed 3mo 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
platform-skills
Practical guidance for platform engineers across Claude, Codex, Cursor, and Copilot: Kubernetes (baseline, RBAC, workload hardening, debug), GitHub Actions (design, security, review, debug), Azure (Workload Identity, tagging, AKS, RBAC), OpenShift (SCC, Routes, GitOps, upgrades), Secrets (ESO, Sealed Secrets, rotation.
figma-console-mcp-skills
The full collection: design tokens (export/import/setup), variable and library management, component-set analysis and docs, WCAG and design-system linting, accessibility audits, version history, changelog, blame, comments, annotations, FigJam, and Slides.
design-mastery
Master design through principles, legendary designers, and historical movements. Build professional brand identities with systematic workflows.
canvas-to-code-marketplace
Single-plugin marketplace for Canvas-to-Code — translates canvas designs (HTML + screenshot) into design-system-aligned code through eleven explicit gates.
canvas-to-code
Translate canvas designs (HTML + screenshot) into design-system-aligned code through eleven explicit gates.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.