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/rube-de/cc-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/rube-de/cc-skills/pm)<a href="https://agentmods.dev/plugins/rube-de/cc-skills/pm"><img src="https://agentmods.dev/badge/plugins/rube-de/cc-skills/pm/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/rube-de/cc-skills/pm"><img src="https://agentmods.dev/badge/plugins/rube-de/cc-skills/pm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pm 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 4d 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": "pm",
"description": "GitHub issue lifecycle: brainstorm design approaches, create structured issues for LLM agent teams, triage and recommend next issues, audit and clean up stale backlogs, and deep-validate individual issues against the codebase",
"version": "2.21.1",
"source": "./plugins/pm",
"category": "productivity",
"author": {
"name": "rube-de",
"url": "https://github.com/rube-de"
},
"keywords": [
"project-management",
"github-issues",
"issue-creation",
"task-planning",
"issue-triage",
"issue-audit",
"issue-review",
"backlog-management"
]
}What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 425 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#pm 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.
- 4d ago Changed 507751adad0a
- 10d ago Changed d57bf1caa747
- 13d ago Changed 64405043e140
- 14d ago Changed f47098743e2b
- 15d ago Changed 5b50d8ab257d
- 17d ago Changed 8d1f3c11a55b
- 27d ago Changed f727417ad152
- 1mo ago Changed 9500508506a5
- 1mo ago First seen · 21 lines scan A 51dc922a87c3
pm is a plugin published in the GitHub repository rube-de/cc-skills (10 stars, last pushed 4d 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
han-linear
Linear-facing extensions to the Han suite. Adds work-items-to-linear, which creates one Linear issue per slice from a work-items file. Works through the Linear MCP server and requires it to be configured. Depends on no other Han plugin. Opt-in: installed on its own, not pulled in by the han meta-plugin.
lets
Development workflow with session management, code review, and task tracking.
fullstack-dev-kit
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
great-cto
You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 72 specialist agents — an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…
asdlc
Agentic SDLC workflows: plan a spec or Jira ticket with a human approval gate, build it task by task, review PRs with a three-lens council, and run a pre-delivery quality check.