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-epicgit clone --depth 1 https://github.com/evb87-tech/corpusWhat 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 | $0.00050 | $0.00637 |
| Opus 5 | $0.00025 | $0.00318 |
| Sonnet 5 | $0.00010 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
pm-epic 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 2d 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 userConfig 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 <path> pour créer un vault, puis exporter le chemin." >&2
exit 1
fi
Vérifier que $CORPUS_VAULT/.corpus-vault existe. Sinon, refuser et demander à l'utilisateur de lancer /init-vault <path>.
Validation de l'argument :
$ARGUMENTS doit être fourni. Si absent, afficher :
Usage : /pm-epic <chemin-vers-prd>
Le chemin peut être absolu ou relatif à $CORPUS_VAULT/output/.
Exemple : /pm-epic output/2024-01-15-feature-search.md
et s'arrêter.
Résoudre le chemin du PRD :
- 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-decomposer (voir corpus-pm/agents/pm-decomposer.md) en lui passant le chemin absolu résolu du PRD.
Le sous-agent s'occupe de :
- Lire et parser le PRD.
- Créer l'epic dans beads via
bd create. - Créer une issue enfant par exigence P0/P1 via
bd create. - Lier chaque enfant à l'epic via
bd dep add. - Afficher le récapitulatif final (epic ID, IDs enfants, chemin PRD).
Contrainte anti-lissage : le sous-agent doit refuser de créer une issue si les critères d'acceptation sont absents pour une exigence P0. Ne jamais inventer des critères.
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.
- 2d ago First seen · 49 lines · 50 tokens per session scan A 0ad109f97caf
pm-epic is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 637 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
om-tidy
Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits oversized notes, reports stale open loops, fixes links. Safe by construction: never deletes, never commits, zero content loss.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
om-capture-1on1
Take a meeting transcript, notes, or Gemini summary and create a structured vault note with key takeaways, quotes, action items, and DM context.
om-peer-scan
Deep scan a peer's GitHub PRs for performance review preparation. Produces a structured analysis saved to perf/evidence/.
om-weekly
Weekly synthesis — cross-session review of vault activity, North Star alignment, patterns, uncaptured wins, and forward priorities.
om-dump
Freeform capture mode. Dump anything — conversations, decisions, incidents, wins, thoughts — and I'll route it all to the right notes with proper templates, frontmatter, and wikilinks.