brain-jam-plan

brain-jam-plan is a skill for Claude Code from povvo/claudikins-kernel. It costs 54 tokens per session (1,704 once invoked), scanned A, original, MIT.

A planning method for discussing requirements and technical options step by step before coding. It keeps a person involved throughout the process and presents trade-offs between possible approaches.

In plain words
What is it for?
Use it to clarify the problem, define success, identify what is out of scope, compare implementation choices, and create a plan for complex changes.
Why use it?
It reduces confusion when requirements are changing or several solutions could work. The discussion helps prevent missed constraints and unnecessary work.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool.

Part of the claudikins-kernel plugin — 4 skills, 4 commands, 7 agents, 8 hooks shipped together

Good fit Use it to clarify the problem, define success, identify what is out of scope, compare implementation choices, and create a plan for complex changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/povvo/claudikins-kernel/brain-jam-plan
Install

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.

Any agent
npx skills add povvo/claudikins-kernel --skill brain-jam-plan
Clone the repo
git clone --depth 1 https://github.com/povvo/claudikins-kernel

Made for: Claude Code.

Or install claudikins-kernel, the plugin that ships this one along with the rest of its 4 skills, 4 commands, 7 agents, 8 hooks.

Wrote 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.

agentmods badge for brain-jam-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/povvo/claudikins-kernel/brain-jam-plan/github.svg)](https://agentmods.dev/skills/povvo/claudikins-kernel/brain-jam-plan)
Your own site
<a href="https://agentmods.dev/skills/povvo/claudikins-kernel/brain-jam-plan"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-kernel/brain-jam-plan/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.

agentmods 80×15 button for brain-jam-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/povvo/claudikins-kernel/brain-jam-plan"><img src="https://agentmods.dev/badge/skills/povvo/claudikins-kernel/brain-jam-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,704 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.01704
Opus 5.5 $0.00022 $0.00682
Sonnet 5.5 $0.00011 $0.00341
Haiku 4.5 $0.00005 $0.00170

Measured 2mo ago against content hash e131c314601f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

brain-jam-plan 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 2mo 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.

skills/brain-jam-plan/SKILL.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Brain-Jam Planning Methodology

Overview

Planning is an iterative conversation, not a production line. The human stays in the loop at every phase.

"Go back and forth with Claude until I like its plan. A good plan is really important." — Boris

Core principle: Understand before solving. Ask before assuming. Recommend but let user decide.

Trigger Symptoms

Use this skill when:

  • Running the claudikins-kernel:outline command
  • Requirements are unclear or keep changing
  • Multiple valid approaches exist and you can't choose
  • User wants involvement in decisions (not just receive a plan)
  • Previous plans failed due to missed requirements
  • Scope creep is a concern
  • You're tempted to just start coding without a plan

The Brain-Jam Process

Phase 1: Requirements Gathering

One question at a time. Wait for the answer.

Key questions to answer:

  1. What problem are we solving?
  2. What does success look like?
  3. What constraints exist?
  4. What's explicitly OUT of scope?

Use AskUserQuestion with specific options — never open-ended unless necessary.

Phase 2: Context Building

Before proposing solutions, understand the landscape:

  • What exists already in the codebase?
  • What patterns should we follow?
  • What dependencies apply?
  • What has been tried before?

Phase 3: Approach Generation

Generate 2-3 distinct approaches. Each must include:

Element Purpose
Summary 1-2 sentence overview
Pros Clear benefits
Cons Honest trade-offs
Effort low / medium / high
Risk low / medium / high

Always recommend one with reasoning. See approach-template.md.

Phase 4: Section-by-Section Drafting

Draft one section at a time. Get approval before moving on.

Never batch approvals — each checkpoint is a chance to course-correct.

Non-Negotiables

These rules have no exceptions:

One question at a time.

Read the full file on GitHub · 205 lines

Changes

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.

  1. 2mo ago First seen · 205 lines · 54 tokens per session scan A e131c314601f

Subscribe to this mod's changes

brain-jam-plan is a skill published in the GitHub repository povvo/claudikins-kernel (127 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 1,704 once invoked, about $0.0002 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-30.

Related

brain-jam-plan compared with skills from other repositories

brain-jam-plan next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
brain-jam-planpovvo/claudikins-kernelSkill1276mo agoMITA54Claude Code
task-breakdowncentminmod/claude-pluginsSkill1911d agononeA177Claude Code
audit-session-metricscentminmod/claude-pluginsSkill1911d agononeA147Claude Code
session-metricscentminmod/claude-pluginsSkill1911d agononeB182Claude Code
opikcomet-ml/opik-claude-code-pluginSkill2515d agoApache-2.0A80Claude Code
design-webfusengine/agentsSkill3425d agoMITA36Claude Code
solid-phpfusengine/agentsSkill3425d agoMITA35Claude Code