gestion-commandes

gestion-commandes is a skill for Claude Code, Codex from PrendsTaPart/Plugin-Claude-MCP-BraindCode-. It costs 42 tokens per session (1,144 once invoked), scanned A, original, Apache-2.0.

A French-language tool for managing restaurant orders. It follows a fixed order sequence from waiting and confirmation through preparation, readiness, delivery, or cancellation.

In plain words
What is it for?
Use it to create orders, track active orders, and change their status, such as confirmed, being prepared, ready, or delivered.
Why use it?
It keeps order changes in the correct sequence and requires the restaurant and product details to be resolved before an order is changed.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the foodeatup plugin — 22 skills, 5 agents shipped together

Install

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.

agentmods
npx agentmods add skills/prendstapart/plugin-claude-mcp-braindcode-/gestion-commandes
Any agent
npx skills add PrendsTaPart/Plugin-Claude-MCP-BraindCode- --skill gestion-commandes
Clone the repo
git clone --depth 1 https://github.com/PrendsTaPart/Plugin-Claude-MCP-BraindCode-

Made for: Claude Code, Codex.

Or install foodeatup, the plugin that ships this one along with the rest of its 22 skills, 5 agents.

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.

agentmods badge for gestion-commandes

README.md
[![agentmods](https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/gestion-commandes.svg)](https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/gestion-commandes)
Your own site
<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>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,144 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 70b991ce3261, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

foodeatup/skills/gestion-commandes/SKILL.md · 80 lines

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)

  1. Charger ${CLAUDE_PLUGIN_ROOT}/reference/directives-outils.md et appliquer ses règles pendant toute l'exécution (IDs, confirmations, données, formats, erreurs).
  2. S'assurer d'avoir l'establishment_id (le demander si absent) avant tout appel.
  3. 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_entities AVANT tout autre appel — fuzzy FR géré par le serveur (accents, pluriels) ; si ambiguous=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

  1. Créer une commandecreate_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_reservation et seat_waitlist créent DÉJÀ la commande — ne pas en créer une seconde pour la même table ;
    • LIVRAISON/EMPORTER : customer_name, customer_phone, customer_address si livraison ;
    • la création génère AUTOMATIQUEMENT facture + devis : ne pas appeler create_invoice en plus.
  2. Suivrelist_orders (filtres) / get_order : commandes en cours par statut ; croiser avec floor_plan_status pour la vue salle.
  3. Avancer les statutsupdate_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 (voir service-salle).
  4. Annulationupdate_order_status avec annulee : action irréversible, confirmation explicite obligatoire, motif consigné en note.

Read the full file on GitHub · 80 lines

Changes

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.

  1. 4d ago First seen · 80 lines · 42 tokens per session scan A 70b991ce3261

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens