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.
npx skills add rube-de/cc-skills --skill pmgit 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/skills/rube-de/cc-skills/pm)<a href="https://agentmods.dev/skills/rube-de/cc-skills/pm"><img src="https://agentmods.dev/badge/skills/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/skills/rube-de/cc-skills/pm"><img src="https://agentmods.dev/badge/skills/rube-de/cc-skills/pm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 329 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 115 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00098 | $0.04009 |
| Opus 5 | $0.00049 | $0.02005 |
| Sonnet 5 | $0.00020 | $0.00802 |
| Haiku 4.5 | $0.00010 | $0.00401 |
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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Manager
GitHub issue lifecycle: brainstorm, create, triage, audit, and review.
Sub-Skills
| Skill | Command | Description |
|---|---|---|
| Create | /pm or /pm -quick <desc> |
Create structured issues optimized for agent execution |
| Brainstorm | /pm:brainstorm |
Explore problem space and design approaches before creating issues |
| Next | /pm:next |
Triage open issues — recommend what to work on next |
| Update | /pm:update |
Audit open issues — find stale, orphaned, and drift |
| Review | /pm:review ISSUE_NUMBER |
Deep-validate a single issue against the codebase |
Usage
/pm → Create a new issue (interactive flow)
/pm -quick fix the login → Create issue with smart defaults
/pm brainstorm caching → Explore approaches before creating issues
/pm:brainstorm → Same (alternate syntax)
/pm next → Triage: recommend next issue to work on
/pm:next → Same (alternate syntax)
/pm update → Audit: find stale/orphaned issues
/pm:update → Same (alternate syntax)
/pm review 42 → Review: validate issue #42 against codebase
/pm:review 42 → Same (alternate syntax)
Routing
Parse the first argument:
| Argument | Route to |
|---|---|
brainstorm |
/pm:brainstorm sub-skill |
next |
/pm:next sub-skill |
update |
/pm:update sub-skill |
review |
/pm:review sub-skill |
-quick [desc] |
Create Issue Workflow (quick mode) below |
| anything else / empty | Create Issue Workflow below |
If routed to a sub-skill, invoke it with Skill and pass remaining arguments. If the first
argument is -quick, skip the Ambiguity Check and go directly to the Create Issue Workflow
(quick mode is an explicit signal that the user wants fast issue creation, not brainstorming).
Otherwise, continue with the Ambiguity Check below.
Ambiguity Check
Before starting the Create Issue Workflow, check for existing specs and assess readiness.
What ships with it
2 files beside SKILL.md 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.
- 9d ago First seen · 388 lines · 98 tokens per session scan A 9ad0a0113cf0
pm is a skill published in the GitHub repository rube-de/cc-skills (10 stars, last pushed 3d ago), licensed MIT. It adds 98 tokens to every session and 4,009 once invoked, about $0.0005 per session on Opus 5. 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 skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
vertical-construction
Domain knowledge for the construction vertical (contractors, field crews) so architect and pm don't spec construction products naively. Covers the vocabulary (bid vs estimate, takeoff, retainage, change order, AIA G702/G703, lien waiver, draw schedule), the non-obvious money rules that incumbents like Procore price…