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 ai-swiss/base --skill metier-communicationgit clone --depth 1 https://github.com/ai-swiss/baseWrote 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/ai-swiss/base/metier-communication)<a href="https://agentmods.dev/skills/ai-swiss/base/metier-communication"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/metier-communication/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/ai-swiss/base/metier-communication"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/metier-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.01758 |
| Opus 5 | $0.00018 | $0.00879 |
| Sonnet 5 | $0.00007 | $0.00352 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
metier-communication 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 9d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Métier: Communication professionnelle
Connaissances métier sur la communication professionnelle pour PME et startups, avec un focus sur le marché suisse romand.
LinkedIn: bonnes pratiques
Structure d'un bon post
- Accroche: la première ligne est cruciale. C'est elle qui décide si le lecteur clique «voir plus». Elle doit interpeller, surprendre ou poser une question.
- Corps: 2 à 3 paragraphes courts. Alterner informations et réflexions personnelles.
- Appel à l'action: question ouverte, invitation à commenter, ou lien vers une ressource.
- Hashtags: 3 à 5 hashtags pertinents, placés en fin de post.
Longueur idéale
- Post court: 50 à 100 mots, idéal pour une réflexion, une citation, une question
- Post standard: 150 à 300 mots, idéal pour raconter une expérience, partager un apprentissage
- Post long: 300 à 500 mots, à utiliser avec parcimonie, pour un sujet qui le mérite
Fréquence et timing
- Fréquence conseillée: 2 à 3 posts par semaine pour maintenir la visibilité
- Jours optimaux: mardi, mercredi, jeudi
- Heures optimales: 7h-9h (avant le travail) ou 12h-14h (pause déjeuner)
- À éviter: vendredi après-midi, week-end (sauf si l'audience est B2C)
Engagement
- Répondre aux commentaires dans les 2 premières heures renforce la visibilité
- Les posts avec une opinion personnelle génèrent plus d'engagement que les annonces factuelles
- Les images et documents augmentent la portée (mais pas les liens externes, que LinkedIn pénalise)
Types de posts qui fonctionnent
| Type | Quand l'utiliser |
|---|---|
| Storytelling | Partager une expérience vécue, un apprentissage |
| Éducatif | Expliquer un concept, donner des conseils pratiques |
| Coulisses | Montrer l'équipe, le quotidien, l'envers du décor |
| Témoignage | Partager un retour client ou un succès projet |
| Question | Lancer un débat, solliciter l'avis de la communauté |
| Actualité | Réagir à une tendance, une nouvelle du secteur |
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.
- 9d ago First seen · 138 lines · 37 tokens per session scan A 2905ac7a72a6
metier-communication is a skill published in the GitHub repository ai-swiss/base (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,758 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-30.
Other skills, from other repositories
wallet-cli
Operate the TypeScript TRON wallet CLI for accounts, transfers, staking, governance, contracts, signing, chain queries, and password input with wallet-cli 4.13.0. Refuse wallet passwords in argv and require the supported stdin channel. For Java REPL requests, refuse that entry and offer the TypeScript one-shot CLI…
compliance
Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…
vault
Operate Joel's Obsidian Vault through the joelclaw CLI. Use when reading ADRs/projects, searching notes, listing PARA sections, or auditing ADR hygiene with vault adr commands. Triggers on: 'check the vault', 'read ADR', 'find this note', 'vault search', 'ADR collisions', 'ADR audit', 'decision inventory', or any…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.