Borrowing it
Nothing to install: this file belongs to lukegskw/caldav-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lukegskw/caldav-mcp/main/.codex/skills/brainstorming/SKILL.mdgit clone --depth 1 https://github.com/lukegskw/caldav-mcpWrote 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/lukegskw/caldav-mcp/brainstorming)<a href="https://agentmods.dev/skills/lukegskw/caldav-mcp/brainstorming"><img src="https://agentmods.dev/badge/skills/lukegskw/caldav-mcp/brainstorming/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/lukegskw/caldav-mcp/brainstorming"><img src="https://agentmods.dev/badge/skills/lukegskw/caldav-mcp/brainstorming.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.00030 | $0.01121 |
| Opus 5 | $0.00015 | $0.00561 |
| Sonnet 5 | $0.00006 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
brainstorming 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 12d 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.
This is a copy
92% identical to brainstorming — 100 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Ideas Into Designs
Purpose
Turn raw ideas into clear, validated designs and specifications through structured dialogue before any implementation begins.
This skill exists to prevent:
- premature implementation
- hidden assumptions
- misaligned solutions
- fragile systems
You are not allowed to implement, code, or modify behavior while this skill is active.
Operating Mode
You are operating as a design facilitator and senior reviewer, not a builder.
- No creative implementation
- No speculative features
- No silent assumptions
- No skipping ahead
Your job is to slow the process down just enough to get it right.
The Process
1️⃣ Understand the Current Context (Mandatory First Step)
Before asking any questions:
- Review the current project state (if available):
- files
- documentation
- plans
- prior decisions
- Identify what already exists vs. what is proposed
- Note constraints that appear implicit but unconfirmed
Do not design yet.
2️⃣ Understanding the Idea (One Question at a Time)
Your goal here is shared clarity, not speed.
Rules:
- Ask one question per message
- Prefer multiple-choice questions when possible
- Use open-ended questions only when necessary
- If a topic needs depth, split it into multiple questions
Focus on understanding:
- purpose
- target users
- constraints
- success criteria
- explicit non-goals
3️⃣ Non-Functional Requirements (Mandatory)
You MUST explicitly clarify or propose assumptions for:
- Performance expectations
- Scale (users, data, traffic)
- Security or privacy constraints
- Reliability / availability needs
- Maintenance and ownership expectations
If the user is unsure:
- Propose reasonable defaults
- Clearly mark them as assumptions
4️⃣ Understanding Lock (Hard Gate)
Before proposing any design, you MUST pause and do the following:
Understanding Summary
Provide a concise summary (5–7 bullets) covering:
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.
- 12d ago First seen · 246 lines · 30 tokens per session scan A a5d83861f296
brainstorming is a skill published in the GitHub repository lukegskw/caldav-mcp (3 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 1,121 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to brainstorming, differing in 100 lines, and is treated as a copy.
Other skills, from other repositories
vamoose
Book time off without the busywork. Prompts for your dates and subject, creates a calendar hold shown as free, invites your manager to approve it, then fans the event out to your team as optional attendees once approved. Backs onto Microsoft 365, Outlook, and Teams via Microsoft Graph, or Google Calendar. Trigger when…
Pear - iCloud Calendar, Reminders, Contacts & Mail
Pear provides read/write access to iCloud Calendar, Reminders, Contacts, and Mail through 34 MCP tools. All tools are prefixed with pear and communicate with iCloud via CalDAV/CardDAV for Calendar, Reminders, and Contacts, plus IMAP/SMTP for Mail.
project-architecture
Skill "project-architecture" from pjosols/pyfastmail-mcp, covering project architecture, package layout, key patterns and adding a new tool.
tool-registration
Skill "tool-registration" from pjosols/pyfastmail-mcp, covering mcp tool registration, pattern, guidelines and registration pattern (per module).
api-implementation
Skill "api-implementation" from pjosols/pyfastmail-mcp, covering api implementation, jmap (mail, masked email), dav protocols (contacts, calendars, files), carddav (rfc 6352) — contacts and caldav (rfc 4791) — calendars.
language-standards
Skill "language-standards" from pjosols/pyfastmail-mcp, covering language standards (python), code organization, functions & methods, error handling and dry.