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 pr-authoringgit 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/pr-authoring)<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/pr-authoring"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/pr-authoring/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/pr-authoring"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/pr-authoring.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.00065 | $0.01404 |
| Opus 5.5 | $0.00026 | $0.00562 |
| Sonnet 5.5 | $0.00013 | $0.00281 |
| Haiku 4.5 | $0.00006 | $0.00140 |
Grade A, and why
pr-authoring 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 16d 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 — 108 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.
PR Authoring — playbook
A PR is a contract with the reviewer, exactly as a PRD is a contract with engineering. The reviewer must understand what happened, what they are approving, what could go wrong, and how to undo it — without opening the diff or the chat history.
Format adopted 2026-07-22 from the Symphony engineering-handoff pattern (ajayd942/cloudflare-ai-event-concierge#4).
Related contracts: ticket-authoring (the upstream ticket this PR closes —
its acceptance criteria become this PR's evidence rows) and pr-review
(what the reviewer owes back). The full chain:
PRD story → ticket → PR → review → merge → deploy. When starting a new product repo,
copy .github/PULL_REQUEST_TEMPLATE.md from great-pm into that repo's
.github/ so GitHub auto-fills every new PR with this skeleton.
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.
- 16d ago First seen · 108 lines · 65 tokens per session scan A 5b4339486109
pr-authoring is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 17d ago), licensed MIT. It adds 65 tokens to every session and 1,404 once invoked, about $0.0003 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
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy. Use when PR preparation or commit strategy is needed.
batch-member-cites-a-path-only-a-non-member-adds
You wrote something correct that the default reader cannot reach: a batch member citing a path only a NON-member adds, or a rule, ruling or ledger sitting on an unlanded branch.
working-tree-edits-stranded-on-squash-merge
Diagnose and prevent "I made the fix but it's not on main" cases where the fix was applied in the working tree via Edit / Write but never git added before the squash-merge. Use when: (1) you squash-merged a PR and the user reports the issue is back, (2) git status after the merge shows uncommitted changes for files…
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.