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 agentmods add skills/prendstapart/plugin-claude-mcp-braindcode-/gestion-commandesnpx skills add PrendsTaPart/Plugin-Claude-MCP-BraindCode- --skill gestion-commandesgit 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-/gestion-commandes)<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/gestion-commandes"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/gestion-commandes.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 | $0.00042 | $0.01144 |
| Opus 5 | $0.00021 | $0.00572 |
| Sonnet 5 | $0.00008 | $0.00229 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
gestion-commandes 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 4d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gestion des commandes
Étape 0 — Références et établissement (obligatoire)
- Charger
${CLAUDE_PLUGIN_ROOT}/reference/directives-outils.mdet appliquer ses règles pendant toute l'exécution (IDs, confirmations, données, formats, erreurs). - S'assurer d'avoir l'
establishment_id(le demander si absent) avant tout appel. - Règle « Résolution des noms » (directives § 1 ter) : tout nom parlé ou
écrit (produit, ingrédient, plat, équipement, table, recette) se résout
via
search_entitiesAVANT tout autre appel — fuzzy FR géré par le serveur (accents, pluriels) ; siambiguous=true, présenter les candidats et DEMANDER confirmation avant d'agir. Jamais d'ID deviné.
Machine à états des commandes (à respecter strictement)
en_attente → confirmee → en_preparation → prete → livree (+ annulee).
Pas de saut d'étape en avant (une commande ne passe pas de en_attente à
prete) ; annulee possible depuis tout état non terminé mais avec
confirmation explicite de l'utilisateur.
Workflow
- Créer une commande —
create_order(establishment_id,items=[{name, quantity, unit_price, tax_rate}]) :- prix et TVA depuis
list_dishes/list_products— jamais de tête (TVA selon la nature : immediate 10 %, conservable 10 %/5,5 %, alcohol 20 %) ; service_mode∈ livraison | emporter | sur_place ;channel(défaut manuel) ;covers;- SUR PLACE : passer
table_id— la commande est liée à la table du plan de salle. Rappel :checkin_reservationetseat_waitlistcréent DÉJÀ la commande — ne pas en créer une seconde pour la même table ; - LIVRAISON/EMPORTER :
customer_name,customer_phone,customer_addresssi livraison ; - la création génère AUTOMATIQUEMENT facture + devis : ne pas appeler
create_invoiceen plus.
- prix et TVA depuis
- Suivre —
list_orders(filtres) /get_order: commandes en cours par statut ; croiser avecfloor_plan_statuspour la vue salle. - Avancer les statuts —
update_order_status(establishment_id,order_id,status) en respectant la machine à états.- Effets de bord automatiques : le statut se répercute sur la facture/devis
liés, et une commande payée passe la table en
cleaning— ne pas déplacer la table à la main en plus (voirservice-salle).
- Effets de bord automatiques : le statut se répercute sur la facture/devis
liés, et une commande payée passe la table en
- Annulation —
update_order_statusavecannulee: action irréversible, confirmation explicite obligatoire, motif consigné en note.
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.
- 4d ago First seen · 80 lines · 42 tokens per session scan A 70b991ce3261
gestion-commandes is a skill published in the GitHub repository PrendsTaPart/Plugin-Claude-MCP-BraindCode- (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,144 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…