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 C0ntr0lledCha0s/claude-code-plugin-automationsnpx agentmods add plugins/c0ntr0lledcha0s/claude-code-plugin-automations/github-workflowsgit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsGrade A, and why
github-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 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "github-workflows",
"version": "2.0.0",
"description": "Streamlined GitHub workflow automation with 9 core commands and 9 auto-invoking skills. Covers project boards, labels, milestones, commits, issues, pull requests, branching strategies, and worktrees. Features automatic issue tracking, commit integration, branching flow automation (gitflow, GitHub Flow, trunk-based), and session environment setup.",
"author": {
"name": "C0ntr0lledCha0s",
"url": "https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations"
},
"repository": "https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations",
"homepage": "https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations/tree/main/github-workflows",
"license": "MIT",
"keywords": [
"github",
"project-management",
"workflow-automation",
"git",
"project-boards",
"labels",
"milestones",
"milestone-management",
"progress-tracking",
"pull-requests",
"commits",
"issues",
"code-review",
"issue-tracking",
"issue-creation",
"issue-conventions",
"session-setup",
"environment",
"branching",
"gitflow",
"github-flow",
"trunk-based",
"worktrees",
"release-management",
"hotfix"
],
"agents": [
"./agents/workflow-orchestrator.md",
"./agents/pr-reviewer.md",
"./agents/issue-manager.md",
"./agents/release-manager.md"
],
"skills": [
"./skills/creating-issues/",
"./skills/managing-branches/",
"./skills/managing-commits/",
"./skills/managing-projects/",
"./skills/managing-relationships/",
"./skills/managing-worktrees/",
"./skills/organizing-with-labels/",
"./skills/reviewing-pull-requests/",
"./skills/triaging-issues/"
],
"commands": [
"./commands/init.md",
"./commands/workflow-status.md",
"./commands/commit-smart.md",
"./commands/branch-start.md",
"./commanWhat 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 · 68 lines scan A 1f6c4dde93fe
github-workflows is a plugin published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo 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
jira-assistant-skills
Plugin marketplace listing 1 plugin: jira-assistant-skills.
beans-prime
Configure Claude Code to track work using Beans.
rook-claude
Claude Code plugins for rook (github.com/rook/) maintainers: maintainer-grade code review, backlog triage, systemic-PR campaigns, and rook house conventions.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
ai-skills
Plugin marketplace listing 8 plugins: security-hooks, pr-review-triage, dev-skills, nix-skills, git-workflow.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.