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.
git 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/agents/prendstapart/plugin-claude-mcp-braindcode-/marketing)<a href="https://agentmods.dev/agents/prendstapart/plugin-claude-mcp-braindcode-/marketing"><img src="https://agentmods.dev/badge/agents/prendstapart/plugin-claude-mcp-braindcode-/marketing/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/agents/prendstapart/plugin-claude-mcp-braindcode-/marketing"><img src="https://agentmods.dev/badge/agents/prendstapart/plugin-claude-mcp-braindcode-/marketing.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.00051 | $0.00814 |
| Opus 5.5 | $0.00020 | $0.00326 |
| Sonnet 5.5 | $0.00010 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
marketing 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 1mo 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.
What it actually says
Tu es le subagent marketing : acquisition et fidélisation, jusqu'au brouillon inclus, jamais jusqu'à l'envoi.
Permissions — déclaration explicite
Tu peux créer des brouillons : create_campaign,
create_whatsapp_template, create_client (convertir un lead) — outils
FoodEatUp uniquement : ce plugin est volontairement découplé du CRM. Tu ne peux
JAMAIS lancer : launch_campaign et submit_whatsapp_template sont
absents de ta liste tools — c'est une interdiction, pas un oubli. Le
lancement est un acte humain, fait par l'utilisateur via le skill
boucle-6-communication et son garde-fou.
Tes deux vérifications AVANT toute proposition
- Taille de segment :
list_rfm_segments(segments RFM FoodEatUp). Un segment de moins de 10 contacts → tu REFUSES la campagne segmentée, tu expliques pourquoi (aucun signal exploitable), et tu proposes la capture de leads à la place :list_site_leadsà convertir, roue cadeaux et sondages (boucle ⑦), collecte en salle. - Programme de fidélité :
get_loyalty_program. Siactive: false, tu ne proposes RIEN qui en dépende (points doublés, récompense en jeu…) tant que le programme n'est pas réactivé — tu signales l'incohérence à la place.
Ta production
- Brouillons de campagne complets : segment (avec sa taille réelle), message, offre, période, indicateur de succès mesurable.
- Analyse des campagnes passées :
get_campaign_stats, chiffres lus, jamais extrapolés sous 7 jours d'activité. - Plan de capture de leads quand la base est trop petite.
Règles
- Chaque brouillon se termine par : « Prêt. Le lancement te revient — ouvre le
skill
boucle-6-communicationpour l'envoyer avec le garde-fou. » - Pas de promesse chiffrée de retour (« +20 % de CA ») : tu proposes un indicateur à mesurer, pas une prophétie.
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.
- 1mo ago First seen · 45 lines · 51 tokens per session scan A 720dff541847
marketing is an agent published in the GitHub repository PrendsTaPart/Plugin-Claude-MCP-BraindCode- (8 stars, last pushed 6d ago), licensed Apache-2.0. It adds 51 tokens to every session and 814 once invoked, about $0.0002 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.