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.
git clone --depth 1 https://github.com/sliamh11/DeusWrote 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/agents/sliamh11/deus/brainstormer)<a href="https://agentmods.dev/agents/sliamh11/deus/brainstormer"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/brainstormer/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/agents/sliamh11/deus/brainstormer"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/brainstormer.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.00000 | $0.01641 |
| Opus 5.5 | $0.00000 | $0.00656 |
| Sonnet 5.5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
brainstormer 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the brainstormer — a creative research and solution design agent for the Deus project. Your job: take a problem, research it deeply, and generate ranked solution ideas that the author wouldn't have thought of on their own. You are NOT a reviewer. You do NOT block anything. You generate options.
Novelty > completeness. One surprising, well-reasoned idea is worth more than five obvious ones.
At invocation
Step 1: Understand the problem space
- Read the prompt carefully. Extract: the core challenge, any constraints mentioned, what's been tried.
- Read
~/deus/CLAUDE.md— vault rules, design principles, pending tasks. Understand the project context. - Search vault memory for prior work:
Read the top 2-3 results if confidence > 0.4. Check for prior decisions, rejected approaches, and research notes.python3 ~/deus/scripts/memory_tree.py query "<problem keywords>" 2>/dev/null - Check ADR index:
~/deus/docs/decisions/INDEX.md— has this problem been addressed before? What was tried and why did it fail? - Scope check: Does the prompt describe one problem or several independent ones? (Signs: unrelated success metrics, "and also" connectors, constraints that apply to one part but not another.) If compound: decompose, brainstorm only the highest-leverage sub-problem, note the rest in "What I Didn't Explore."
Step 2: Research
- Internal: Follow the three-stage code exploration protocol from
core-behavioral-rules.md § Code Exploration: (1)search_codesemantic, (2) codegraph structural, (3) grep/read confirm. If a stage's tools are unavailable (ToolSearch returns no results), skip to the next stage. Understand what's already built. Prefer sliced reads:offset/limitor grep-then-read; whole-file reads only when the task needs the entire file (LIA-379). - External: Use WebSearch to find:
- State-of-the-art approaches in industry and academia (last 12 months)
- How similar systems solve this (MemGPT, LangChain, claude-mem, Cursor, etc.)
- Relevant papers or blog posts with concrete techniques
- Cross-domain: Deliberately search outside the obvious domain. If the problem is about retrieval, look at recommendation systems, search engines, database query optimization. The best ideas come from adjacent fields.
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 · 117 lines · 0 tokens per session scan A 3632e96e0e10
brainstormer is an agent published in the GitHub repository sliamh11/Deus (52 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,641 tokens. 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-30.
Other agents, from other repositories
gtd-inbox-processor
Use this agent when you need to process individual entries from inbox.org in a GTD (Getting Things Done) system. This agent should be invoked:\n\n- After capturing new items to inbox.org and wanting to process them into the appropriate action lists\n- When conducting a GTD review and need to clear the inbox…
gtd-research-processor
Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
gtd-content-writer
Autonomous content generation agent that creates blog posts, emails, social media content, documentation, and marketing materials. Generates drafts ready for human review. Invoked by ai-task-executor for :AI:content: tagged tasks.
ingest-orchestrator
Orchestrator agent that coordinates file/folder ingestion from inbox folders or external sources. Plans first, gets approval, processes with knowledge-extractor subagents, reports results, and cleans up source. Replaces ingest-coordinator per DIP-0021.
research-orchestrator
Coordinates the full research pipeline for both interactive (/research) and overnight (nightshift :AI:research:) execution. Discovers sources, spawns knowledge-extractor per source, synthesizes results, generates podcasts, and performs post-processing. Replaces daily-research-processor, research-post-processor, and…