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/curiositech/some_claude_skillsWrote 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/curiositech/some_claude_skills/github-actions-pipeline-builder)<a href="https://agentmods.dev/plugins/curiositech/some_claude_skills/github-actions-pipeline-builder"><img src="https://agentmods.dev/badge/plugins/curiositech/some_claude_skills/github-actions-pipeline-builder.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
github-actions-pipeline-builder 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": "github-actions-pipeline-builder",
"description": "Build production CI/CD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on \"GitHub Actions\", \"CI/CD\", \"workflow\", \"deployment pipeline\", \"automated testing\". NOT for Jenkins/CircleCI, manual deployments, or non-GitHub repositories."
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 79 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 · 5 lines scan A cbe7f57e9f99
github-actions-pipeline-builder is a plugin published in the GitHub repository curiositech/some_claude_skills (211 stars, last pushed yesterday), 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-06.
Other plugins, from other repositories
devops-pipeline
CI/CD automation — git worktrees, deploy pipeline, canary monitoring, auto-format/test hooks, and GitHub Actions templates.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
aio-devops
GitHub, GitLab, and git worktree workflows in one toolkit — manage repos, PRs, MRs, pipelines, and parallel branches without juggling CLIs.
charon
Ferries a GitHub PR to merge without waiting forever: an honest snapshot-not-block loop that fixes CI, repairs conflicts, version-checks reviewer suggestions, and never says 'just wait'.
socket-release
Stand up SocketDev publishing (npm, crates.io, GitHub releases, Homebrew tap) in a repo: copy in the release kit and run its bootstrap - name reservation, GitHub environments, npm trusted publisher, staged publish config, verification.
merge-pr
Merge PRs matching repo history conventions. Includes readiness checks, CI watching, stack detection, and automated rebasing.