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 foodeatupWrote 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-/briefing-du-jour)<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/briefing-du-jour"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/briefing-du-jour/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/briefing-du-jour"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/briefing-du-jour.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.01447 |
| Opus 5.5 | $0.00025 | $0.00579 |
| Sonnet 5.5 | $0.00013 | $0.00289 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
briefing-du-jour 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Briefing du jour
É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.
Workflow — collecte (lecture seule, date du jour)
Dérouler dans l'ordre des priorités maison (HACCP > client > rentabilité) :
- Cadre du jour — UN appel serveur —
get_daily_brief(establishment_id) : le brief agrégé côté serveur (alertes du jour, établissement actif). Il ouvre la collecte mais ne la remplace pas — les étapes suivantes vérifient le détail dans chaque registre. - Notifications non lues —
list_notifications(establishment_idseul ; pas de filtre serveur : filtrer les non lues dans la réponse) — elles ouvrent le briefing : ce sont les alertes déposées par le système et les routines (dont Loop Engine). - Conformité HACCP —
list_haccp_temperatures(date du jour) : relevés faits ? valeurs hors seuil ?list_haccp_reception: réceptions à contrôler ? Toute non-conformité passe EN TÊTE du briefing. - Salle & réservations — UN appel temps réel —
floor_plan_status(compteurs par statut + commande active par table) remplace tout appel séparé aux tables/zones.list_reservations(date du jour) reste la source des couverts, gros groupes et notes (allergies, VIP) — l'outil de disponibilité ne renvoie pas les réservations du jour. Puis créneaux chauds du midi :reservation_availabilityteste UN créneau à la fois (date,timeHH:MM,party_size) — sonder 12:00 / 12:30 / 13:00 avec la taille de groupe typique et annoncer la capacité restante (« complet à 12:30, reste 2 tables à 13:00 »). - Staffing —
list_plannings(jour) : qui est présent par service ; croiser avec la charge (couverts attendus) et signaler un sous/sur-staffing. - Productions planifiées —
list_production_plans(date du jour) : quoi produire, en quelle quantité, à quelle heure. - Alertes ingrédients —
list_production_alerts: ingrédients manquants pour les productions à venir. - Stocks bas —
list_low_stocks: articles sous le seuil. - Publier les alertes (seule écriture, sur confirmation) — pour chaque
alerte retenue du briefing (non-conformité HACCP, relevé manquant, stock
critique, surbooking), PROPOSER
create_notification(establishment_id,titlecourt,messagefactuel,type∈warning|danger) pour qu'elle atteigne toute l'équipe dans FoodEatUp. Une confirmation PAR notification ; IDs récapitulés.
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.
- 5d ago Changed · +17 lines d3c3d1579a36
- 1mo ago First seen · 86 lines · 63 tokens per session scan A a288da4c1ff4
briefing-du-jour is a skill published in the GitHub repository PrendsTaPart/Plugin-Claude-MCP-BraindCode- (8 stars, last pushed 6d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,447 once invoked, about $0.0003 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…