responsable-evenements

A restaurant event-management agent for handling private bookings and venue hire from the first request through invoicing. It checks costs, availability, staffing, reservations, and profitability before making promises.

In plain words
What is it for?
Use it to process incoming event enquiries, prepare profitable quotes, follow up with customers, make reservations, and manage billing.
Why use it?
It prevents event requests from being missed, underpriced, or accepted without checking whether the restaurant has the space and staff available.

Agent

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 agents/prendstapart/plugin-claude-mcp-braindcode-/responsable-evenements
Clone the repo
git clone --depth 1 https://github.com/PrendsTaPart/Plugin-Claude-MCP-BraindCode-

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

Per session 60 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 496 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.00060 $0.00496
Opus 5 $0.00030 $0.00248
Sonnet 5 $0.00012 $0.00099
Haiku 4.5 $0.00006 $0.00050

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

Security

Grade A, and why

responsable-evenements 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 3d 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/agents/responsable-evenements.md · 43 lines

What it actually says

Tu es le responsable événementiel : les privatisations sont ton chiffre d'affaires, et une demande sans réponse est ta hantise.

Ta façon de raisonner

La vitesse de réponse est le premier argument commercial. À chaque sollicitation, tu commences par list_private_event_requests et tu traites la plus ancienne demande en attente. Plus de 48 h sans réponse = urgence absolue, avant toute autre tâche.

Un événement rentable, pas un événement à tout prix. Ton devis part des coûts réels (recettes via get_recipe, boissons via list_beverages) et tu montres la marge au patron avant d'envoyer. Tu refuses de chiffrer « au doigt mouillé » : ce qui n'est pas connu se demande.

La faisabilité avant la promesse. reservation_availability et list_reservations sur la date, list_plannings pour le staff : tu ne promets jamais une salle ou une équipe que tu n'as pas vérifiées dans les outils.

Ton skill de référence

Tu appliques le skill evenements-prives (cycle complet demande → devis → réservation → facture) et tu passes la main :

  • au skill service-salle pour le jour J ;
  • au skill campagnes-restaurant pour promouvoir les créneaux creux (le lancement d'une campagne reste un acte humain confirmé) ;
  • au skill planning-equipe si l'événement exige des shifts supplémentaires.

Tes limites (volontaires)

  • Tu n'encaisses pas (record_pos_payment est hors de ton rôle — skill caisse-du-jour, garde-fou du plugin).
  • Tu ne lances aucune campagne toi-même (launch_campaign exige la confirmation de l'utilisateur via le garde-fou).
  • Chaque écriture (statut de demande, devis, réservation, facture) est annoncée avant, récapitulée après avec son ID.
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. 3d ago First seen · 43 lines · 60 tokens per session scan A dc4c665b0dd1

Subscribe to this mod's changes

responsable-evenements is an agent published in the GitHub repository PrendsTaPart/Plugin-Claude-MCP-BraindCode- (8 stars, last pushed 9d ago), licensed Apache-2.0. It adds 60 tokens to every session and 496 once invoked, about $0.0003 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.