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/catlog22/Claude-Code-WorkflowWrote 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/commands/catlog22/claude-code-workflow/from-brainstorm)<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/from-brainstorm"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/from-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/commands/catlog22/claude-code-workflow/from-brainstorm"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/from-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.00018 | $0.03092 |
| Opus 5.5 | $0.00007 | $0.01237 |
| Sonnet 5.5 | $0.00004 | $0.00618 |
| Haiku 4.5 | $0.00002 | $0.00309 |
Grade A, and why
from-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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Mode
When --yes or -y: Auto-select highest-scored idea, skip confirmations, create issue directly.
Issue From-Brainstorm Command (/issue:from-brainstorm)
Overview
Bridge command that converts brainstorm-with-file session output into executable issue + solution for parallel-dev-cycle consumption.
Core workflow: Load Session → Select Idea → Convert to Issue → Generate Solution → Bind & Ready
Input sources:
- synthesis.json - Main brainstorm results with top_ideas
- perspectives.json - Multi-CLI perspectives (creative/pragmatic/systematic)
- .brainstorming/ - Synthesis artifacts (clarifications, enhancements from role analyses)
Output:
- Issue (ISS-YYYYMMDD-NNN) - Full context with clarifications
- Solution (SOL-{issue-id}-{uid}) - Structured tasks for parallel-dev-cycle
Quick Reference
# Interactive mode - select idea, confirm before creation
/issue:from-brainstorm SESSION="BS-rate-limiting-2025-01-28"
# Pre-select idea by index
/issue:from-brainstorm SESSION="BS-auth-system-2025-01-28" --idea=0
# Auto mode - select highest scored, no confirmations
/issue:from-brainstorm SESSION="BS-caching-2025-01-28" --auto -y
Arguments
| Argument | Required | Type | Default | Description |
|---|---|---|---|---|
| SESSION | Yes | String | - | Session ID or path to .workflow/.brainstorm/BS-xxx |
| --idea | No | Integer | - | Pre-select idea by index (0-based) |
| --auto | No | Flag | false | Auto-select highest-scored idea |
| -y, --yes | No | Flag | false | Skip all confirmations |
Data Structures
Issue Schema (Output)
interface Issue {
id: string; // ISS-YYYYMMDD-NNN
title: string; // From idea.title
status: 'planned'; // Auto-set after solution binding
priority: number; // 1-5 (derived from idea.score)
context: string; // Full description with clarifications
source: 'brainstorm';
labels: string[]; // ['brainstorm', perspective, feasibility]
// Structured fields
expected_behavior: string; // From key_strengths
actual_behavior: string; // From main_challenges
affected_components: string[]; // Extracted from description
_brainstorm_metadata: {
session_id: string;
idea_score: number;
novelty: number;
feasibility: string;
clarifications_count: number;
};
}
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 · 383 lines · 18 tokens per session scan A 57958e22bd69
from-brainstorm is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,124 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 3,092 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-30.
Other commands, from other repositories
session-list
List recent sessions from the project ledger and offer to view one.
jira
Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
gofer_hydrate
Reverse-engineer specification from existing code (Hydration).
gofer:check-workspace
Check whether this repo is initialized for Gofer and explain any missing or stale scaffold.
4-finalize
Finalizes a reviewed thread, updates project documentation, and handles cleanup.