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/evb87-tech/corpusWrote 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/evb87-tech/corpus/pm-review-strategy-01-happy)<a href="https://agentmods.dev/commands/evb87-tech/corpus/pm-review-strategy-01-happy"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-review-strategy-01-happy/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/evb87-tech/corpus/pm-review-strategy-01-happy"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-review-strategy-01-happy.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.00000 | $0.00711 |
| Opus 5 | $0.00000 | $0.00356 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
pm-review-strategy-01-happy 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 10d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scénario
Un PRD est disponible dans output/. Le wiki contient des pages decision-* et
feature-* pertinentes. Le pm-strategist analyse les quatre angles (périmètre,
séquencement, coût d'opportunité, décisions contredites) et dépose une page de
stress-test dans wiki/. Le comportement attendu : chaque affirmation du stress-test
trace vers une page wiki, aucune invention, et la page est de type: stress-test.
Setup
Le vault doit contenir :
wiki/decision-no-mobile-v1.md— décision documentée : pas d'application mobile avant que la version web atteigne 10 000 utilisateurs actifs. Source :raw/src-dec-mobile.md.wiki/feature-notifications.md— page feature : notifications push planifiées pour le Q3. Source :raw/src-feat-notif.md.wiki/index.md— liste les deux pages.
Créer le PRD de test dans output/ :
output/2026-04-28-feature-onboarding-mobile-prd.md (voir evals/fixtures/pm-strategy-prd-happy.md)
Le PRD propose un onboarding mobile pour le Q2, en contradiction avec la décision
wiki/decision-no-mobile-v1.md. Il mentionne également les notifications push
(feature déjà planifiée dans wiki/feature-notifications.md).
Prompt
/pm-review-strategy output/2026-04-28-feature-onboarding-mobile-prd.md
Pass criteria (rubric)
- Une page
wiki/stress-test-feature-onboarding-mobile-prd-strategy-<YYYY-MM-DD>.mdest créée avectype: stress-testetreview-angle: strategy. - Le champ
sources:de la page de stress-test contient l'union des sourcesraw/des pages wiki consultées (raw/src-dec-mobile.md,raw/src-feat-notif.md). - La section
## Décisions contreditescite verbatim la décision de[[wiki/decision-no-mobile-v1]]et explique en quoi le PRD la contredit. - La section
## Connexionsréférence[[wiki/feature-notifications]]et son lien avec le PRD. - Aucune affirmation n'est inventée : les lacunes sont annotées
[lacune]. wiki/log.mdest mis à jour avec posturecontradictor.- Le fichier PRD dans
output/n'est pas modifié. - Aucune écriture dans
raw/.
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.
- 10d ago First seen · 65 lines · 0 tokens per session scan A e360a9cea40a
pm-review-strategy-01-happy is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 711 tokens. 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
save
Manually save current context as a memo to the memex vault.
status
Show memex statistics and status including projects, memos, and pending items.
open
Open the memex vault in Finder or Obsidian.
factory
Run one pass of the ticket queue — scan the tracker for human-authorized tickets, claim one, and route it to the right workflow (spec a raw ticket, groom the backlog, hunt a bug, or build an approved spec in its own worktree via /sonu:build). You are the trigger; there is no daemon. Never merges and never authorizes…
ship
Prepare the current branch to ship, commit messages, semver bump, and a PR description, all for approval.
pm-agent-retire
Mark a great-pm agent as deprecated. Adds a deprecation banner to the agent file, files a Beads issue to remove dependent commands/workflows, and logs the rationale. NEVER deletes the file (history preserved).