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 SebastianElvis/reaper --skill brainstormgit clone --depth 1 https://github.com/SebastianElvis/reaperWrote 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/sebastianelvis/reaper/brainstorm)<a href="https://agentmods.dev/skills/sebastianelvis/reaper/brainstorm"><img src="https://agentmods.dev/badge/skills/sebastianelvis/reaper/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/sebastianelvis/reaper/brainstorm"><img src="https://agentmods.dev/badge/skills/sebastianelvis/reaper/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.00043 | $0.01768 |
| Opus 5 | $0.00022 | $0.00884 |
| Sonnet 5 | $0.00009 | $0.00354 |
| Haiku 4.5 | $0.00004 | $0.00177 |
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 9d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
The recurring ideation step. Reads the current research state and proposes new or refined ideas for investigation. This skill is lightweight and fast — it generates ideas, not experiments.
Usage
Invoke this skill by name; pass an optional context hint as a quoted string. On slash-command hosts, prefix with / (e.g. /brainstorm "<hint>").
# Generate ideas based on current state
brainstorm
# With a hint about what direction to explore
brainstorm "explore liveness under partial synchrony"
Relationship to Other Skills
/formalize-problemhandles initial formalization: pinning down trust assumptions, the core question, definitional hygiene, and the first set of hypotheses. It runs once./brainstormhandles recurring ideation: generating additional ideas as the investigation progresses. It runs many times./investigatehandles execution: deep-diving into specific ideas. It does not generate new hypotheses.
Inputs
Always read before starting:
reaper-workspace/notes/problem-statement.md— model assumptions and property definitionsreaper-workspace/notes/ideas.md— the current ideas and their resolution statusreaper-workspace/notes/current-understanding.md— the "branch tip" of accumulated knowledgereaper-workspace/notes/results.md— what's been tried and what happened. If the file is long (20+ rows), read the batch summaries at the end instead of every individual row. Look for patterns in failures across batches, not individual cycle details.
Lazy-load only when needed (skip these unless you're stuck or exploring a specific direction):
reaper-workspace/notes/paper-summary.md— the source paper (if provided)reaper-workspace/notes/literature.md— known prior workreaper-workspace/notes/clarified-goal.md— refined research goal and scopereaper-workspace/papers/— downloaded PDFs and per-paper notes- The optional context hint from the argument
Process
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.
- 9d ago First seen · 150 lines · 43 tokens per session scan A 0b259f991884
brainstorm is a skill published in the GitHub repository SebastianElvis/reaper (9 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,768 once invoked, about $0.0002 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
literature-review-agent
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the literature search strategy from outline.json — discover candidate papers via web search, verify them through Semantic Scholar (Levenshtein > 70 fuzzy title match, temporal cutoff, dedup by paperId), cross-corroborate against Crossref + OpenAlex to…
agent-research-aggregator
Pre-pipeline aggregator that scans AI agent cache directories (.claude, .cursor, .antigravity, .openclaw) or any user-specified directory for experimentation logs, extracts insights and numeric results, and formats them as PaperOrchestra-ready inputs (idea.md + experimentallog.md). TRIGGER when the user says…
content-refinement-agent
Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate…
paper-orchestra
Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines, optional figures) into a submission-ready LaTeX manuscript and compiled PDF. TRIGGER when the user asks to "write a paper…
section-writing-agent
Step 4 of the PaperOrchestra pipeline (arXiv:2604.05018). ONE single multimodal LLM call that drafts the remaining paper sections (Abstract, Methodology, Experiments, Conclusion), extracts numeric values from experimentallog.md into LaTeX booktabs tables, splices the generated figures from Step 2, and merges…
outline-agent
Step 1 of the PaperOrchestra pipeline (arXiv:2604.05018). Convert (idea.md, experimentallog.md, template.tex, conferenceguidelines.md) into a strict JSON outline containing a plotting plan, literature search plan (Intro + Related Work), and section-level writing plan with citation hints. TRIGGER when the orchestrator…