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 boucle-1-configurationgit 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-/boucle-1-configuration)<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/boucle-1-configuration"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/boucle-1-configuration.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.00087 | $0.00652 |
| Opus 5 | $0.00044 | $0.00326 |
| Sonnet 5 | $0.00017 | $0.00130 |
| Haiku 4.5 | $0.00009 | $0.00065 |
Grade A, and why
boucle-1-configuration 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 8d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boucle ① — Configuration (référentiels de l'établissement)
Quand l'utiliser
Pour diagnostiquer la complétude et la cohérence des référentiels d'un établissement déjà créé : catégories, TVA, unités, zones, tables, équipements. C'est la boucle amont — toutes les autres échouent silencieusement si elle est trouée (un plat sans TVA, une salle sans tables, un relevé HACCP sans équipement).
Enchaînement d'outils MCP (l'ordre compte)
search_entitiessi l'establishment_idn'est pas connu (le demander sinon).- Lectures, dans cet ordre :
list_categories,list_tva,list_units,list_zones,list_tables, puislist_dishesetlist_productspour croiser. - Croisement : chaque plat/produit doit pointer vers une catégorie et une TVA existantes ; chaque zone doit contenir au moins une table.
- Corrections à la demande :
create_category/update_category,create_tva,create_zone,create_table,create_dish_category,create_equipment.
Règles métier
- TVA restauration France : 10 % sur place/à emporter alimentaire, 20 % alcool, 5,5 % produits emballés — vérifier qu'aucun taux exotique ne traîne.
- Un équipement froid déclaré sans relevé de température récent est un trou de boucle ④, à signaler ici comme « équipement configuré mais non suivi ».
- Ne jamais inventer une valeur absente : écrire « non déclaré ».
Garde-fous (opérations exigeant confirmation)
delete_categoryest intercepté par le hook du plugin (confirmation humaine) : une suppression de catégorie orpheline ses produits.- Aucune autre écriture de cette boucle n'est destructive, mais toute écriture se fait après récapitulatif (« je vais créer X, Y — d'accord ? »).
Sortie attendue
Un tableau [référentiel | présent | trous détectés | correction proposée] puis
la liste des écritures proposées, en attente d'accord explicite.
Ce que ce skill NE fait PAS
- Installer un établissement de zéro → skill
onboarding-restaurateur(plugin foodeatup). - Construire la carte en ligne → skill
carte-vitrine(plugin foodeatup). - Le paramétrage du site vitrine relève de la boucle ⑤ → skill
boucle-5-ecommerce.
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.
- 8d ago First seen · 52 lines · 87 tokens per session scan A bf1c7747080e
boucle-1-configuration is a skill published in the GitHub repository PrendsTaPart/Plugin-Claude-MCP-BraindCode- (8 stars, last pushed 15d ago), licensed Apache-2.0. It adds 87 tokens to every session and 652 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.