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 VandanaAjayDubey111/great-pm --skill great-pm-runtimegit clone --depth 1 https://github.com/VandanaAjayDubey111/great-pmWrote 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/vandanaajaydubey111/great-pm/great-pm-runtime)<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/great-pm-runtime"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/great-pm-runtime/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/vandanaajaydubey111/great-pm/great-pm-runtime"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/great-pm-runtime.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00032 | $0.00444 |
| Opus 5.5 | $0.00013 | $0.00178 |
| Sonnet 5.5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
great-pm-runtime 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
GreatPM Codex Runtime
Before starting a workflow, run:
node ../../scripts/great-pm-codex-doctor.mjs
If it reports an uninitialized workspace, stop and present its exact next step.
- Resolve the selected role under
../../agents/; for example, the orchestrator role is../../agents/pm-lead.md. - Keep two distinct names: the canonical role from that file and the internal
spawn identifier. For
task_nameoragent_name(whichever the exposed tool schema accepts), replace every hyphen with an underscore:query-refiner-pm→query_refiner_pm,pm-lead→pm_lead. Identifiers must match^[a-z0-9_]+$. Each packaged role lists its identifier. Preserve canonical names in prompts, filenames, verdict logs, and user-facing output: usegrill-me, nevergrill. Do not rename skills or role files. Record canonical role, internal identifier, and returned agent ID together. - Call the Codex
spawn_agentcollaboration tool with the role, initiative, expected artefact, dependencies, human-gate boundary, and DONE/BLOCKED contract. A prose promise to delegate is not a spawn. - Store the agent identifier returned by every successful spawn. Never call
wait_agentor another wait tool with an empty target set, and never wait before at least one spawn has returned an identifier. - Spawn independent roles concurrently.
- Never impersonate a role when subagent tools are unavailable or a spawn fails; report BLOCKED and name the missing capability.
- Collect each verdict without rewriting it.
- Persist role verdicts under
.great-pm/verdicts/. - Only the human may approve
gate:strategy,gate:spec, orgate:launch.
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 · 36 lines · 32 tokens per session scan A 92a466ea098c
great-pm-runtime is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 444 once invoked, about $0.0001 per session on Opus 5.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-09-21.
Other skills, from other repositories
caixun-work-hours
A work-hours reporting assistant for RichPMS, a project time-tracking system. It turns conversation details, code records, or your description into a daily report, lets you confirm it, and then saves or submits it.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
nexus-configuration
A skill for reading, planning, approving, and checking configuration in Nexus, the current private conversation or room. It covers settings such as agents, rooms, providers, channels, connectors, skills, models, tools, and MCP connections.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, UI mockups, product shots, or transparent-background cutouts. Use when the result should be an image asset rather than repo-native SVG, HTML/CSS, or canvas.
sherpa
Guiding workflows by decomposing complex tasks (Epics) into Atomic Steps under 15 minutes each, with progress tracking and drift prevention. Use when complex decomposition is needed.
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.