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 agentmods add commands/evb87-tech/corpus/pm-review-strategygit 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)<a href="https://agentmods.dev/commands/evb87-tech/corpus/pm-review-strategy"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-review-strategy.svg" alt="Measured on agentmods" 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.00061 | $0.00704 |
| Opus 5 | $0.00030 | $0.00352 |
| Sonnet 5 | $0.00012 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
pm-review-strategy 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 5d 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
Pré-vol :
CORPUS_VAULT="${CORPUS_VAULT:-$CLAUDE_PLUGIN_OPTION_VAULT_PATH}"
if [ -z "$CORPUS_VAULT" ]; then
echo "Vault non configuré. Définir CORPUS_VAULT (dev local) ou configurer l'option utilisateur vaultPath dans le plugin installé (exposée comme CLAUDE_PLUGIN_OPTION_VAULT_PATH). Ni l'un ni l'autre n'est défini. Lancer /init-vault <chemin> pour initialiser un vault, puis exporter le chemin." >&2
exit 1
fi
Vérifier que $CORPUS_VAULT/.corpus-vault existe. Sinon, refuser et demander au propriétaire de lancer /init-vault <chemin>. Voir corpus-core/rules/08-vault-structure.md.
Validation de l'argument :
$ARGUMENTS doit être fourni. Si absent, afficher :
Usage : /pm-review-strategy <chemin-vers-brouillon>
Le chemin peut être absolu ou relatif à $CORPUS_VAULT/output/.
Exemple : /pm-review-strategy output/2026-04-28-ma-feature-prd.md
et s'arrêter.
Résoudre le chemin du brouillon :
- Si
$ARGUMENTSest un chemin absolu, l'utiliser tel quel. - Sinon, le résoudre sous
$CORPUS_VAULT/output/:$CORPUS_VAULT/output/$ARGUMENTS(supprimer le préfixeoutput/s'il est déjà présent).
Vérifier que le fichier résolu existe et se trouve bien sous $CORPUS_VAULT/output/. Si le fichier n'existe pas ou est en dehors de output/, refuser avec un message explicite.
Délégation :
Déléguer au sous-agent pm-strategist (voir corpus-pm/agents/pm-strategist.md) en lui passant le chemin absolu résolu du brouillon.
Le sous-agent s'occupe de :
- Lire le brouillon.
- Scanner
wiki/decision-*etwiki/feature-*. - Analyser les quatre angles : périmètre, séquencement, coût d'opportunité, décisions contredites.
- Déposer la page de stress-test dans
$CORPUS_VAULT/wiki/stress-test-<draft-slug>-strategy-<YYYY-MM-DD>.md. - Mettre à jour
wiki/log.md.
Contrainte anti-lissage : si le wiki ne contient aucune page decision-* ni feature-*, le sous-agent doit refuser avec un arrêt dur et orienter le propriétaire vers /ingest. Il ne doit jamais inventer des décisions ou des éléments de roadmap absents du wiki.
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.
- 5d ago First seen · 49 lines · 61 tokens per session scan A 505638e7cede
pm-review-strategy is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 704 once invoked, about $0.0003 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
discover
Generate a substantive project note for the current (or specified) repo. Forces a fresh discovery — if a project note already exists, appends a new ## SuperBrain discovery (date) section without clobbering existing content. Use when SuperBrain didn't auto-discover (e.g., the project's slug collided with a note…
inject
Inject freeform text into the SuperBrain vault. SuperBrain splits multi-topic input, places each item in the right scope (project / decision / capture / etc.), links related notes, and updates today's daily note. Short single-blob input is preserved verbatim; longer or multi-paragraph input is split via the inject…
adopt
Adopt an existing directory as the SuperBrain vault (marks it, indexes existing notes).
migrate
Import an existing Obsidian vault into SuperBrain's structure — non-destructive (source is read-only; SuperBrain's vault gets copies). Optional path argument; otherwise Claude finds the vault.
save
Manually save current context as a memo to the memex vault.
status
Show memex statistics and status including projects, memos, and pending items.