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 launch-readinessgit 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/launch-readiness)<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/launch-readiness"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/launch-readiness/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/launch-readiness"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/launch-readiness.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.00037 | $0.01109 |
| Opus 5.5 | $0.00015 | $0.00444 |
| Sonnet 5.5 | $0.00007 | $0.00222 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
launch-readiness 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex host binding
- Treat references to Claude slash workflows as the equivalently named Codex skill.
- Before delegating to any specialist, read the
great-pm-runtimeskill and the selected packaged role file. - Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex
spawn_agentcall with that role and a bounded assignment. - For the spawn tool's
task_nameoragent_nameidentifier, replace canonical role-name hyphens with underscores (query-refiner-pm→query_refiner_pm). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename. - Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
- If
spawn_agentis unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set. - Resolve bundled paths from the installed GreatPM plugin root.
- Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
- Preserve GreatPM human gates, governance, state, and reporting contracts.
Launch Readiness — playbook
A launch is a phased exposure, not a switch. Plan the cohorts, the gates, and the rollback path before the first user sees the change.
1. Phased rollout — the four typical phases
- Internal — team uses it on prod data, with full instrumentation.
- Beta cohort — a curated, small group of real users (10–100).
- Canary — a slice of the user base (1% → 10% → 50%).
- General availability (GA) — all users.
Each phase has a gate. The gate is testable: "X is true OR pause." Skipping a phase is fine if the risk is genuinely low — but say so out loud.
2. Beta cohort design
- Who: users who match the target audience AND will give feedback — heavy users, vocal users, design partners.
- Size: 10–100 typically. Below 10 is anecdotal; above 100 is hard to support.
- Duration: 1–4 weeks. Long enough to surface real usage; not so long users disengage.
- Feedback loop: a defined channel (a Slack room, a weekly call, an in-product survey). Without this it is just a small launch.
- Exit criteria: testable conditions to advance — usage frequency, satisfaction, defect rate, support volume.
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 · 100 lines · 37 tokens per session scan A df3d3bd574a2
launch-readiness is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,109 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.