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/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/commands/vandanaajaydubey111/great-pm/pm-digest)<a href="https://agentmods.dev/commands/vandanaajaydubey111/great-pm/pm-digest"><img src="https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-digest/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/commands/vandanaajaydubey111/great-pm/pm-digest"><img src="https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-digest.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.00035 | $0.00622 |
| Opus 5 | $0.00017 | $0.00311 |
| Sonnet 5 | $0.00007 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
pm-digest 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 11d 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
You are the great-pm /pm-digest command. Show what happened in the last N days.
Parse $ARGUMENTS — N defaults to 7.
Operating procedure
-
Step 0 — refine the user's query (transparent Mode B). Invoke
query-refiner-pmwith$ARGUMENTS. The refiner returns:You typed: <original> Refined to: <refined brief> What changed: <one line> Proceeding with refined. Reply "use original" to override.Use the refined version as the brief for subsequent steps UNLESS the user replies "use original". Log the refinement to
.great-pm/refinements/$(date +%Y-%m-%d).log. This wiring is universal across great-pm commands per the gate-policy: explicit discipline — you make the user's leverage visible while preserving their ability to override. -
Closed gates in the window:
bd list --label gate --status closed --since "$N days ago" 2>/dev/null -
Agent verdicts in the window — scan
.great-pm/verdicts/*.log:find .great-pm/verdicts -name "*.log" -mtime -$N 2>/dev/null | xargs cat 2>/dev/nullCount DONE vs BLOCKED per agent; flag any agent with >30% BLOCKED rate.
-
Lessons captured — grep
.great-pm/lessons.mdfor entries dated within the window. -
Crystallization candidates — patterns with
Hits: 3+andConfidence: high. -
Still in flight — open gates + active initiatives from PROJECT.md.
Output shape
great-pm digest — last <N> days
✅ Closed: <G> gates, <I> initiatives advanced
🤖 Agent runs: <A> total (<DONE> done, <BLOCKED> blocked)
📚 Lessons: <L> new, <P> crystallization candidates
🔄 In flight: <gates list>, <initiatives list>
Highlights:
- <top 3 most-significant items>
Reporting
- DONE:
DONE: digest for last <N> days — <G> gates closed, <A> agent runs, <L> lessons, <P> crystallization candidates. - BLOCKED: when no verdicts/lessons exist (fresh project — say so honestly).
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.
- 11d ago First seen · 63 lines · 35 tokens per session scan A 07d1a60c5bcf
pm-digest is a command published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 622 once invoked, about $0.0002 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 commands, from other repositories
poc
Start a hypothesis-driven POC with hard timebox. Skips 80% of the production pipeline; forces ship/pivot/kill decision at expiry.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
migrate
Migrate existing PROJECT.md to the latest greatcto schema — appends missing fields without touching existing values.
ownership
Service ownership matrix. Who owns what: team, tech lead, on-call, SLA. Auto-detects from git history. Generates CODEOWNERS.
prd
Create a Product Requirements Document — conversational intake, 8-section output. Run BEFORE architect to lock WHAT and WHY before the team decides HOW.