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-2-equipegit 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-2-equipe)<a href="https://agentmods.dev/skills/prendstapart/plugin-claude-mcp-braindcode-/boucle-2-equipe"><img src="https://agentmods.dev/badge/skills/prendstapart/plugin-claude-mcp-braindcode-/boucle-2-equipe.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.00079 | $0.00602 |
| Opus 5 | $0.00039 | $0.00301 |
| Sonnet 5 | $0.00016 | $0.00120 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
boucle-2-equipe 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 7d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boucle ② — Équipe (staffing, contrats, congés, recrutement)
Quand l'utiliser
Pour un état de santé RH de l'établissement : effectifs, couverture du planning, congés en attente, pointages anormaux, recrutements en cours. Le but est de détecter les trous de service avant qu'ils n'arrivent en salle.
Enchaînement d'outils MCP (l'ordre compte)
list_employees(effectif actif), puislist_employee_contracts(contrats manquants ou expirés — un employé actif sans contrat est une alerte).list_planningssur les 7 prochains jours, croisé aveclist_reservations(boucle ⑤) : un pic de couverts sans shift correspondant = trou de staffing.list_leaves(demandes en attente → proposerapprove_leave/reject_leaveune par une, jamais en lot),list_attendances(pointages incohérents).- Recrutement :
list_job_applicationsetupdate_application_status;create_job_offer/update_job_offersi un poste reste découvert. - Actions courantes :
create_shift,assign_task.
Règles métier
- Une demande de congé n'est jamais approuvée sans vérifier la couverture du planning sur les dates concernées.
- Un trou de staffing se qualifie avec les réservations réelles, pas au ressenti.
- Les documents employés (
list_employee_documents) se consultent, ne se divulguent pas : pas de données personnelles dans la synthèse.
Garde-fous (opérations exigeant confirmation)
Interceptés par le hook du plugin (confirmation humaine obligatoire) :
create_employee_contract— acte juridique ;update_employee_schedule— modifie le planning contractuel ;delete_employee— suppression irréversible.
Sortie attendue
Un tableau [sujet | état | risque | action proposée] sur 5 sujets : effectif,
couverture planning, congés, pointages, recrutement. Trois actions maximum.
Ce que ce skill NE fait PAS
- Construire ou remanier le planning shift par shift → skill
planning-equipe(plugin foodeatup). - Les projets/Kanban d'équipe hors restaurant → plugin rapidorh.
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.
- 7d ago First seen · 51 lines · 79 tokens per session scan A c2f0b0ee4d40
boucle-2-equipe is a skill published in the GitHub repository PrendsTaPart/Plugin-Claude-MCP-BraindCode- (8 stars, last pushed 13d ago), licensed Apache-2.0. It adds 79 tokens to every session and 602 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
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.