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/siva01c/claude-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/siva01c/claude-plugins/cicd-tools)<a href="https://agentmods.dev/plugins/siva01c/claude-plugins/cicd-tools"><img src="https://agentmods.dev/badge/plugins/siva01c/claude-plugins/cicd-tools/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/siva01c/claude-plugins/cicd-tools"><img src="https://agentmods.dev/badge/plugins/siva01c/claude-plugins/cicd-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cicd-tools 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": "cicd-tools",
"description": "CI/CD pipeline skills for Drupal projects — GitLab CI and GitHub Actions authoring, testing, and drush-based deployment",
"version": "1.0.0",
"author": {
"name": "Ludek Kvapil - siva01"
}
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 174 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.
- 1mo ago First seen · 9 lines scan A 63d15f397891
cicd-tools is a plugin published in the GitHub repository siva01c/claude-plugins (16 stars, last pushed 20d 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-30.
Other plugins, from other repositories
pm-autopilot
Put recurring rituals on autopilot: charter what to automate, schedule it on any runner (Claude Code routines, cron, n8n, GitHub Actions), and make every run delta-aware so it reports what changed, not what it already said. Ships with the recurring skills worth scheduling.
devops
DevOps & Cloud — Infrastructure, delivery, reliability, and the arithmetic of running things in production.
famulor
Operate Famulor assistants, calls, history, campaigns, messaging, telephony, knowledge, dashboards, automations, and workspace settings through OAuth-secured MCP tools.
famulor-assistants-history
Review Famulor assistants and read omnichannel call, messaging, and email history through an OAuth-secured, read-only 11-tool MCP profile.
famulor
Operate Famulor assistants, history, campaigns, messaging, telephony, knowledge, analytics, and more through the OAuth-secured MCP server and bundled agent skill.
beeyev-skills
Agent skills by beeyev: GitLab CI/CD pipelines and more.