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 PrendsTaPart/Plugin-Claude-MCP-BraindCode- --skill ideation-iteration-planninggit clone --depth 1 https://github.com/PrendsTaPart/Plugin-Claude-MCP-BraindCode-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.
[](https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/ideation-iteration-planning)<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/ideation-iteration-planning"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/ideation-iteration-planning/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/prendstapart/plugin-claude-mcp-braindcode-/ideation-iteration-planning"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/ideation-iteration-planning.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.00545 |
| Opus 5.5 | $0.00012 | $0.00218 |
| Sonnet 5.5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
ideation-iteration-planning 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.
What it actually says
Iteration Planning
Catégorie : Idéation
Durée : 45-60 min
Pourquoi
Planifier l'itération V2 pendant que la V1 est fraîche garantit le momentum et l'amélioration continue.
Objectif
Planifier le sprint pour la V2.
Livrable attendu
Backlog priorisé + sprint plan
Étape 0 — Contexte (obligatoire)
Charger ./rapido-kb/ — surtout ./rapido-kb/startup/ (vision, persona,
offre, hypothèses construits par dossier-startup-360 et
interview-business-plan). La KB PRIME : ne jamais redemander une
information déjà validée, la reformuler pour confirmation. Les chiffres
réels viennent des MCP — jamais de mémoire ; tout chiffre sans source datée
porte la mention « hypothèse fondateur, confiance faible ».
Étapes
- Compiler le backlog — Feedbacks + idées + bugs
- Prioriser avec RICE — Reach × Impact × Confidence / Effort
- Définir le scope V2 — Réaliste pour 2-4 semaines
- Découper en tâches — Assignables et mesurables
- Planifier le sprint — Timeline et milestones
Pro tips
- Moins de features, plus de polish
- Inclus du temps pour les bugs imprévus
- Un sprint = un objectif clair
Erreurs fréquentes
- Scope trop ambitieux
- Pas de buffer pour les imprévus
- Ignorer la dette technique
Données & serveurs MCP
- RapidoCRM (
rapidocrm) — données réelles, lecture d'abord - RapidoRh (
rapidorh) pour décliner en projet/tâches
Livrable — toujours dans la KB du client
Écrire le livrable daté dans
./rapido-kb/startup/forge/ideation/ideation-iteration-planning.md (le dossier du client,
dans SON répertoire de travail — jamais dans le plugin). Si des chiffres
clés en sortent, proposer de mettre à jour
./rapido-kb/startup/business-plan/hypotheses.md (source + date).
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 · 66 lines · 30 tokens per session scan A 120a852300f2
ideation-iteration-planning is a skill published in the GitHub repository PrendsTaPart/Plugin-Claude-MCP-BraindCode- (8 stars, last pushed 6d ago), licensed Apache-2.0. It adds 30 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.