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-brainstormgit 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.00057 | $0.00520 |
| Opus 5 | $0.00028 | $0.00260 |
| Sonnet 5 | $0.00011 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
pm-brainstorm 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 yesterday.
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éfinissez CORPUS_VAULT (dev local) ou configurez l'option utilisateur vaultPath dans le plugin installé (exposée sous CLAUDE_PLUGIN_OPTION_VAULT_PATH). Ni l'un ni l'autre n'est défini. 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.
Validation de l'argument :
$ARGUMENTS doit être fourni. Si absent, afficher :
Usage : /pm-brainstorm <idée produit>
Décrivez l'idée en texte libre. Exemple : /pm-brainstorm notifications push pour les utilisateurs mobiles inactifs
et s'arrêter.
Idée à tester : $ARGUMENTS
Invoquez la skill corpus-pm:brainstorm pour conduire la séance de pression-test. 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 d'analyse, la taxonomie des axes, les règles de citation et le comportement de signalement des lacunes se trouvent dans la skill.
Chemins : tous relatifs à $CORPUS_VAULT.
Quand terminé, rapportez :
- Chemin du fichier brainstorm produit dans
output/ - Pages wiki citées (liste)
- Lacunes signalées (dimensions sans données wiki)
- Verdict de la séance (idée renforcée / affaiblie / incertaine)
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.
- yesterday First seen · 41 lines · 57 tokens per session scan A f7154a803523
pm-brainstorm is a command published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 520 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-vault-upgrade
Import and migrate content from an existing Obsidian vault into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults.
om-self-review
Write your self-assessment for your company's review tool. Produces project impact descriptions, competency self-assessments (current level / next level), principles, and growth plan — all within character limits, fact-checked, strategically calibrated.
om-vault-audit
Deep structural audit of the vault. Checks indexes, folder placement, frontmatter, links, Bases, and consistency. Fix what can be fixed, flag what needs user input.
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-intake
Process all unread meeting notes in work/meetings/ — reads each file, classifies content, routes to the right vault notes, then clears the inbox.
om-wrap-up
Full session review before ending. Review context, ways of working, files modified, consistency, and suggest improvements.