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 bnet47/codexicon --skill brainstormgit clone --depth 1 https://github.com/bnet47/codexiconWrote 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/bnet47/codexicon/brainstorm)<a href="https://agentmods.dev/skills/bnet47/codexicon/brainstorm"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/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/bnet47/codexicon/brainstorm"><img src="https://agentmods.dev/badge/skills/bnet47/codexicon/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.00025 | $0.00545 |
| Opus 5.5 | $0.00010 | $0.00218 |
| Sonnet 5.5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorm
Announce: "I'm using brainstorm to resolve the feature choices before implementation."
1. Load relevant project context
Read root SPEC.md and TASKS.md when present plus only the architecture, conventions, decisions, or prior specs relevant to the feature. If the repository is still unconfigured, route to $discover so the root contract is created.
2. Resolve the problem
Ask only genuinely blocking questions, batching related questions when practical, and stop when you can state:
- the problem and affected person;
- verifiable success;
- constraints and non-goals;
- the smallest shippable slice;
- unresolved risks.
3. Compare approaches
Present two or three genuinely viable approaches with tradeoffs in behavior, complexity, reversibility, and verification. Recommend one and explain why. Ask for a choice only when the alternatives materially change the product or cost; otherwise proceed with the recommended reversible option and state the assumption.
4. Write the spec
After the direction is clear, append the requirements, interfaces, acceptance, anti-goals, assumptions, and a dated amendment to the root SPEC.md in place. Use the existing contract sections; do not create a separate brainstorm artifact:
## Amendments
- **[YYYY-MM-DD]:** [Chosen direction and rationale.]
Put the chosen problem, solution, acceptance, non-goals, constraints, first slice,
and open questions in the matching root SPEC.md sections before adding the dated
amendment entry.
Run python scripts/codexicon.py spec-check. Self-check that every criterion is testable, no placeholder remains, anti-goals are explicit, and the first slice is complete rather than scaffolding. For authorized implementation, use $write-plan to create or validate TASKS.md, then enter the shared $autonomous-build loop without a routine approval turn. Use task states TODO, ACTIVE, BLOCKED, and DONE; queue outcomes are READY, RESUME_ACTIVE, BLOCKED, COMPLETE, and INVALID.
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 Changed · -17 lines fbbb91ca5cff
- 1mo ago Changed · -1 tokens per session 8547a08b8698
- 1mo ago First seen · 63 lines · 26 tokens per session scan A da70d7ac84b8
brainstorm is a skill published in the GitHub repository bnet47/codexicon (5 stars, last pushed 20d ago), licensed MIT. It adds 25 tokens to every session and 545 once invoked, about $0.0001 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
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
make_plan
For external plan request scenarios, guides the Agent to request a clear, actionable, step-by-step plan from a stronger Agent via listagents and chatwithagent, emphasizing that the plan is executed by the requester, not by the consulted Agent.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.