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 bootcamp-stakeholder-mappinggit 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-/bootcamp-stakeholder-mapping)<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/bootcamp-stakeholder-mapping"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/bootcamp-stakeholder-mapping/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-/bootcamp-stakeholder-mapping"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/bootcamp-stakeholder-mapping.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.00038 | $0.00491 |
| Opus 5.5 | $0.00015 | $0.00196 |
| Sonnet 5.5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
bootcamp-stakeholder-mapping 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
Analyse des Parties Prenantes
Bootcamp 5 jours — Jour 1
Catégorie : Étude de Marché
Framework : Stakeholder Matrix
Durée : 25 min
Objectif
Cartographie tous les acteurs de ton écosystème
É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 parties prenantes — clients, users, payeurs, prescripteurs, régulateurs, partenaires, détracteurs potentiels
- Matrice pouvoir × intérêt — placer chacun dans les 4 quadrants
- Stratégie par quadrant — satisfaire / impliquer / informer / surveiller
- Identifier le champion et le bloqueur — dans le parcours de vente type : qui pousse, qui freine ?
- Plan de contact — pour les 3 acteurs clés : quoi leur dire, quand, par qui
Données & serveurs MCP
- RapidoCRM (
rapidocrm) — données réelles, lecture d'abord
Livrable — toujours dans la KB du client
Écrire le livrable daté dans
./rapido-kb/startup/forge/bootcamp/bootcamp-stakeholder-mapping.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 · 47 lines · 38 tokens per session scan A 5979276a153a
bootcamp-stakeholder-mapping 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 38 tokens to every session and 491 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-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…