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 skills add evb87-tech/corpus --skill brainstormgit 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/skills/evb87-tech/corpus/brainstorm)<a href="https://agentmods.dev/skills/evb87-tech/corpus/brainstorm"><img src="https://agentmods.dev/badge/skills/evb87-tech/corpus/brainstorm/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/skills/evb87-tech/corpus/brainstorm"><img src="https://agentmods.dev/badge/skills/evb87-tech/corpus/brainstorm.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.00079 | $0.02127 |
| Opus 5.5 | $0.00032 | $0.00851 |
| Sonnet 5.5 | $0.00016 | $0.00425 |
| Haiku 4.5 | $0.00008 | $0.00213 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vous conduisez une séance de pression-test (office hours) pour l'idée produit décrite dans $ARGUMENTS, à destination de $CORPUS_VAULT/output/.
Règles fondamentales (anti-lissage)
Ces cinq règles s'appliquent sans exception. Voir corpus-core/rules/07-anti-lissage.md.
- Ne jamais harmoniser les contradictions. Si deux pages wiki se contredisent sur le positionnement ou les personas, citez les deux, attribuez chacune à sa source, et signalez le conflit dans la section concernée.
- Ne jamais inventer une source. Chaque claim tracé dans le rapport doit correspondre à une page wiki existante dans
$CORPUS_VAULT/wiki/. Si vous ne pouvez pas le tracer, vous ne pouvez pas l'écrire. - Ne jamais compléter silencieusement avec des connaissances d'entraînement. Si le wiki est silencieux sur une dimension, dites-le explicitement. N'injectez pas de savoir général sur le marché, les personas génériques ou les tendances sectorielles.
- Ne jamais lisser la voix du propriétaire. Si des pages
decision-*oupositioning-*contiennent des formulations singulières, citez-les verbatim ou paraphrasez minimalement. La singularité est la valeur. - Ne jamais produire ce rapport comme page wiki. Ce rapport est une synthèse produit ; il va dans
output/, jamais danswiki/. Voircorpus-core/rules/04-output-drafting.md.
Phase 1 — Collecte des entités wiki
- Lisez
$CORPUS_VAULT/wiki/index.mdpour identifier les pages pertinentes. - Collectez dans cet ordre de priorité :
Glob $CORPUS_VAULT/wiki/positioning-*.md— positionnement produitGlob $CORPUS_VAULT/wiki/decision-*.md— engagements et décisions passéesGlob $CORPUS_VAULT/wiki/persona-*.md— personas documentésGlob $CORPUS_VAULT/wiki/segment-*.md— segments de marchéGlob $CORPUS_VAULT/wiki/competitor-*.md— concurrents documentésGlob $CORPUS_VAULT/wiki/feature-*.md— fonctionnalités connexes existantes
- Lisez chaque page trouvée en entier avant d'analyser.
- Si
wiki/index.mdest absent ou vide, signalez-le et lisez directement les fichiers globbés.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 157 lines · 79 tokens per session scan A d66d2eb32ba6
brainstorm is a skill published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 5mo ago), licensed MIT. It adds 79 tokens to every session and 2,127 once invoked, about $0.0003 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 skills, from other repositories
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
superbrain-recall
Search the user's SuperBrain second-brain vault. Use whenever the user references past work, prior decisions, "how did we", "did we already", earlier sessions, a project's history, or anything that may already be recorded — before answering from scratch.
garden-tending
Tend the knowledge garden — diagnose vault health, condense project memos into project.md overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what…
curator-practice
Operating philosophy for autonomous memex curator tending — orientation protocol, signal triage, bounded work units, initiative thresholds, logging conventions. Trigger on cron-launched runs with no user prompt, "use your judgment", "tend without instructions", "do a pass on the vault", "I'll be away — do what needs…
memo-writing
How to write effective session memos — format, frontmatter schema, observation extraction, topic-signal append. Trigger on /memex:save, "save this for later", "remember this", "save what we discussed", "document this session", "create a memo", or when the [memex] activity nudge appears in context. Do NOT trigger for…
recall
Retrieve session memory across 4 modes — TEMPORAL (date browsing), KEYWORD (FTS lookup), DEEP (cross-session synthesis), LOAD (specific file). Trigger on "what did I do yesterday/last week", "why did we...", "remind me...", "find the memo about...", "last time we...", "patterns across projects", "load the X topic". Do…