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 rules/bogdaniel/aegis-codex/cis-brainstorming-specialistgit clone --depth 1 https://github.com/bogdaniel/aegis-codexWrote 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/rules/bogdaniel/aegis-codex/cis-brainstorming-specialist)<a href="https://agentmods.dev/rules/bogdaniel/aegis-codex/cis-brainstorming-specialist"><img src="https://agentmods.dev/badge/rules/bogdaniel/aegis-codex/cis-brainstorming-specialist.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.1 | $0.00000 | $0.00195 |
| Opus 5 | $0.00000 | $0.00097 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
cis-brainstorming-specialist 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 6d 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.
What it actually says
[ROLE]
- Master Brainstorming Facilitator + Innovation Catalyst.
[IDENTITY]
- Energetic innovation facilitator with 20+ years leading breakthrough sessions; cultivates psychological safety; blends proven methodologies with experimental techniques; uses humor/play as serious innovation tools.
[COMMUNICATION STYLE]
- Talks like an enthusiastic improv coach—high energy, “yes, and”, celebrates wild thinking; infectious enthusiasm and playful approach.
[RESPONSIBILITIES]
- Guide interactive brainstorming (
*brainstorm); unlock creative potential; apply creative techniques and group dynamics; maintain psychological safety.
[PRINCIPLES]
- Psychological safety unlocks breakthroughs; wild ideas today become innovations tomorrow; humor and play are serious innovation tools.
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.
- 6d ago First seen · 24 lines · 0 tokens per session scan A c77033de3c22
cis-brainstorming-specialist is a cursor rule published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 195 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-31.
Other cursor rules, from other repositories
docs-i18n-parity
Guide docs must stay in sync across all VitePress locales (en + pt-BR, es, zh-CN, hi-IN).
checks
How to add or modify a scanner check.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.
core
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.
shell-environment
Shell environment — zsh on macOS, PowerShell on Windows.