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-spec)<a href="https://agentmods.dev/commands/evb87-tech/corpus/pm-spec"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-spec/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-spec"><img src="https://agentmods.dev/badge/commands/evb87-tech/corpus/pm-spec.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.00047 | $0.00658 |
| Opus 5.5 | $0.00019 | $0.00263 |
| Sonnet 5.5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
pm-spec 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.
What it actually says
Pré-vol :
CORPUS_VAULT="${CORPUS_VAULT:-$CLAUDE_PLUGIN_OPTION_VAULT_PATH}"
if [ -z "$CORPUS_VAULT" ]; then
echo "Aucun vault configuré. Définissez CORPUS_VAULT (dev local) ou configurez l'option utilisateur vaultPath dans le plugin installé (exposée sous CLAUDE_PLUGIN_OPTION_VAULT_PATH). Aucune des deux n'est définie. Lancez /init-vault <chemin> pour initialiser un vault, puis exportez le chemin." >&2
exit 1
fi
Vérifiez que $CORPUS_VAULT/.corpus-vault existe. Si absent, refusez et indiquez au propriétaire de lancer /init-vault <chemin>. Voir corpus-core/rules/08-vault-structure.md.
Fonctionnalité à spécifier : $ARGUMENTS
Invoquez la skill corpus-pm:feature-spec pour rédiger le PRD. Le préfixe corpus-pm: est obligatoire : Claude Code namespace toujours les skills par plugin et ne résout pas les noms nus, même quand la commande et la skill sont dans le même plugin. Toutes les instructions de rédaction, la taxonomie des sections, les règles de citation et le comportement de signalement des lacunes se trouvent dans la skill.
Chemins : tous relatifs à $CORPUS_VAULT.
Collecte des entités wiki :
- Lisez
wiki/index.mdpour identifier les pages pertinentes. - Collectez dans cet ordre de priorité :
Glob $CORPUS_VAULT/wiki/persona-*.md— personas affectésGlob $CORPUS_VAULT/wiki/competitor-*.md— concurrents pour le positionnementGlob $CORPUS_VAULT/wiki/decision-*.md— engagements préalablesGlob $CORPUS_VAULT/wiki/feature-*.md— fonctionnalités connexes
- Lisez chaque page trouvée en entier avant de rédiger.
Sortie :
- Fichier de sortie :
output/YYYY-MM-DD-<slug>-prd.mdYYYY-MM-DD= date du jour (ISO 8601)<slug>= version kebab-case ASCII de$ARGUMENTS(minuscules, sans accents, sans caractères spéciaux)
- N'écrivez jamais dans
wiki/ni dansraw/.
Quand terminé, rapportez :
- Chemin du fichier PRD produit
- Pages wiki citées (liste)
- Lacunes signalées (sections marquées
[non vérifié]ou mises en attente)
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 · 46 lines · 47 tokens per session scan A d4ae75009e1e
pm-spec is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 658 once invoked, about $0.0002 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-08-31.
Other commands, from other repositories
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…
codex-usage
Show your ChatGPT/Codex weekly usage limits (via the local model-router proxy).
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).
pm-audit
Run the great-pm PM-health audit on a product, an initiative, or great-pm itself. 15 dimensions, severity-rated findings, Top-5 + Quick-Wins + Things-Look-Bad-But-Fine + Open Questions. Files findings as Beads tasks unless --read-only.