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 skills/andresanemic/lore-plugin/brainstorming-lorenpx skills add andresanemic/lore-plugin --skill brainstorming-loregit clone --depth 1 https://github.com/andresanemic/lore-pluginWrote 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/andresanemic/lore-plugin/brainstorming-lore)<a href="https://agentmods.dev/skills/andresanemic/lore-plugin/brainstorming-lore"><img src="https://agentmods.dev/badge/skills/andresanemic/lore-plugin/brainstorming-lore.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 | $0.00127 | $0.03408 |
| Opus 5 | $0.00063 | $0.01704 |
| Sonnet 5 | $0.00025 | $0.00682 |
| Haiku 4.5 | $0.00013 | $0.00341 |
Grade A, and why
brainstorming-lore 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 today.
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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brainstorming-lore — Design changes to the Lore system
Changing the Lore is not like changing code. Code tells you when you broke it; a body of criteria accepts a bad addition silently and keeps reading perfectly well — the cost arrives months later, in a decision that goes the wrong way for a reason nobody can trace back.
So this one slows down on purpose. brainstorming-lore is the bridge between accumulated criterion
and a change to the Lore system itself. It does not begin from a blank prompt: it discovers what
this Entre already knows, makes the unresolved choices visible, and obtains approval before changing
a Lore-owned artifact.
Provenance. Adapted by arbitration from the MIT-licensed
brainstormingskill in Superpowers, copyright © 2025 Jesse Vincent. Lore keeps context-first dialogue, one question at a time, alternatives, proportional design, and explicit approval. It rejects the source's software-only taxonomy, universal activation, forced spec path, automatic commit, and requiredwriting-planshandoff. See Where the source loses below.
Trigger boundary
Invoke this skill only when the user is asking to design what a Lore-owned artifact should contain or how the Lore system should operate, not merely because the request involves ideas or creative work.
Typical triggers:
- create an area, a Lore-governed project scaffold, or a bot through its owner skill;
- design or materially restructure
lore/,FASES.md, a routing contract, or a Lore transmutation; - create or materially modify a Lore Plugin skill;
- a Lore owner skill explicitly requires
brainstorming-lorebefore its threshold.
Second case: a deliverable governed by Lore, not owned by it — 2.3.0
The boundary above asks who owns the artifact, and that question has a blind spot. A batch of posts, a report, a lesson plan or a campaign is not a Lore-owned artifact — and yet the whole design may consist of deciding how to run criteria that is already written: which strategy, which format, which register, which visual family, what the area's process demands next.
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.
- today Changed · +1 lines 59622ad9fd10
- 4d ago First seen · 282 lines · 127 tokens per session scan A 9543cbdf9933
brainstorming-lore is a skill published in the GitHub repository andresanemic/lore-plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 127 tokens to every session and 3,408 once invoked, about $0.0006 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 skills, from other repositories
init
Initialize a personal Trove, a local file-based knowledge index for Claude Code. Use when the user says start/set up/create my trove, or when they want to remember things but no trove exists yet. Scaffolds the trove directory, INDEX.md and entries/ folder at user scope (/.claude/trove, follows you everywhere) or…
remember
Capture a durable learning into the personal Trove. Use when the user says remember this, note this, save to trove, add to my trove, or when a session surfaces a decision, gotcha, convention/preference, or external reference worth keeping. Writes one atomic entry file and updates INDEX.md.
index
Index the repository into Trove memory layers (symbols, modules, subsystems, architecture). Use when the user asks to index the repo, build the trove index, refresh symbols, or re-index after large changes.
query
Progressive retrieval from the Trove index. Use when the user asks what Trove knows about a subsystem, where code lives, or wants context assembled before editing. Runs architecture -> subsystem -> module -> symbol retrieval with a context budget.
context-ingest
The single entry point for getting anything new into your context architecture. Takes any input (documents, URLs, YouTube, meeting notes, pasted content) and triages it: dump to inbox, park in planned, or integrate into active docs. WHEN TO USE: "Here's a document — integrate it into my context" "Save this for later"…
bcos-wiki
Wiki zone manager for BCOS — the universal long-form and cross-cutting content destination per plugin-storage-contract.md Rule 2. Stores runbooks, SOPs, decision logs, how-tos, glossaries, post-mortems, FAQs, meeting notes, and plugin cross-cutting context (charters, transcripts, research, customer-call notes). Two…