Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add PrendsTaPart/Plugin-Claude-MCP-BraindCode-/plugin install foodeatup-bouclesWrote 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-/decouvrir-le-plugin)<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/decouvrir-le-plugin"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/decouvrir-le-plugin.svg" alt="Measured on agentmods" 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.00080 | $0.00667 |
| Opus 5 | $0.00040 | $0.00333 |
| Sonnet 5 | $0.00016 | $0.00133 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
decouvrir-le-plugin 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 6d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Découvrir le plugin (et la marketplace rapido)
Quand l'utiliser
Quand l'utilisateur ne sait pas ce que son installation sait faire. L'audit l'a montré : sans auto-formation, personne ne sait ce que contient le plugin.
Source de vérité
Charger ${CLAUDE_PLUGIN_ROOT}/reference/carte-marketplace.md et répondre
depuis ce fichier — jamais de mémoire. Ce fichier est généré depuis le
dépôt réel par la commande python3 scripts/generer-carte-boucles.py (dépôt de
la marketplace) ; s'il est absent, le dire et indiquer cette commande au lieu
d'improviser une liste.
Ce qu'on présente
- La carte par domaine : restaurant, ventes/CRM, contenu, publicité, vidéo, équipe, direction, sites/apps, formation — avec, pour chaque domaine, les 3 phrases types qui déclenchent le bon skill (elles sont dans la carte).
- Les 8 boucles de ce plugin :
/bouclespour l'état d'ensemble,/boucle <n>pour le détail,/croisementpour les incohérences,/sante-donneespour savoir si les données suffisent. - Ce que ça ne peut PAS faire : la section « limites connues » de la carte (roue cadeaux et sondages en back-office, pas d'envoi ni de publication sans confirmation humaine, rien d'estimé sans outil).
Parcours de démarrage en 5 étapes
- Vérifier la connexion MCP :
get_daily_briefrépond ? Sinon, connecter le serveur FoodEatUp d'abord (prérequis du README du plugin). /boucles— premier état des 8 boucles, lecture seule.- Ouvrir la boucle la plus rouge avec
/boucle <n>et traiter UNE action. /sante-donnees— savoir quelles recommandations sont fiables aujourd'hui.- Quand au moins deux boucles vivent :
/croisementpour les incohérences.
Sortie attendue
Une réponse orientée « prochain geste » : la carte résumée au domaine pertinent pour l'utilisateur, 3 phrases à essayer tout de suite, et l'étape du parcours où il se trouve.
Ce que ce skill NE fait PAS
- Exécuter les boucles elles-mêmes → skills
boucle-1-configurationàboucle-8-comptabiliteetcroisement-service. - Documenter les prompts de la marketplace Braindcode (serveur Braindcode_Plugin) → hors périmètre de ce plugin.
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.
- 6d ago First seen · 54 lines · 80 tokens per session scan A 10df4bc8de2e
decouvrir-le-plugin is a skill published in the GitHub repository PrendsTaPart/Plugin-Claude-MCP-BraindCode- (8 stars, last pushed 12d ago), licensed Apache-2.0. It adds 80 tokens to every session and 667 once invoked, about $0.0004 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…