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-roadmap-productgit 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-roadmap-product)<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/ideation-roadmap-product"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/ideation-roadmap-product/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-roadmap-product"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/ideation-roadmap-product.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.00031 | $0.00684 |
| Opus 5.5 | $0.00012 | $0.00274 |
| Sonnet 5.5 | $0.00006 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
ideation-roadmap-product 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Product
Catégorie : Idéation
Durée : 35-45 min
Pourquoi
Le MVP (Minimum Viable Product) te permet de valider ton hypothèse avec un minimum d'investissement. 90% des fonctionnalités que tu imagines ne seront jamais utilisées - concentre-toi sur l'essentiel.
Objectif
Définir les fonctionnalités essentielles du MVP à développer en premier.
Livrable attendu
Liste priorisée des features MVP avec critères MoSCoW (Must/Should/Could/Won't)
É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
- Lister TOUTES les fonctionnalités — Brainstorme sans filtre - 30+ idées
- Évaluer chaque feature — Impact client (1-5) × Effort de développement (1-5)
- Appliquer MoSCoW — Must (critique), Should (important), Could (nice), Won't (jamais)
- Définir le MVP — Seulement les 'Must' = ton MVP
Prompt: Évalue ces fonctionnalités selon MoSCoW pour un MVP de [PRODUIT] : [LISTE]
- Créer la roadmap — V1 (Must), V1.1 (Should), V2 (Could)
Pro tips
- Le MVP doit résoudre UN problème mieux que quiconque
- Si tu n'as pas honte de ta V1, tu l'as lancée trop tard
- Chaque feature doit avoir un objectif business clair
Erreurs fréquentes
- Trop de 'Must' - sois impitoyable dans ta priorisation
- Construire ce que tu veux vs ce que le client veut
- Oublier les fonctionnalités d'infrastructure (auth, paiement)
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-roadmap-product.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 · 67 lines · 31 tokens per session scan A a3f0c497942b
ideation-roadmap-product 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 31 tokens to every session and 684 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…