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 mrstev3n/balise-skills --skill balise-brand-naminggit clone --depth 1 https://github.com/mrstev3n/balise-skillsWrote 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/mrstev3n/balise-skills/balise-brand-naming)<a href="https://agentmods.dev/skills/mrstev3n/balise-skills/balise-brand-naming"><img src="https://agentmods.dev/badge/skills/mrstev3n/balise-skills/balise-brand-naming/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/mrstev3n/balise-skills/balise-brand-naming"><img src="https://agentmods.dev/badge/skills/mrstev3n/balise-skills/balise-brand-naming.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.00137 | $0.01665 |
| Opus 5 | $0.00068 | $0.00833 |
| Sonnet 5 | $0.00027 | $0.00333 |
| Haiku 4.5 | $0.00014 | $0.00167 |
Grade A, and why
balise-brand-naming 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 12d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explorer le nom et l’identité de marque
Principe central
Traiter les idées initiales du client comme des hypothèses riches, pas comme des conclusions. Faire dériver chaque proposition de nom des fondations de marque, d’un territoire de naming explicite et de preuves vérifiables.
Ne jamais réduire le travail à un nuage de mots ou à des combinaisons automatiques. Un bon candidat peut venir d’un vocabulaire métier, d’une métaphore, d’un patronyme, d’une histoire vécue, d’une expression, d’un lieu ou d’une culture.
Références à consulter
- Lire references/fondations-de-marque.md pour cadrer et rédiger la stratégie minimale.
- Lire references/territoires-de-naming.md avant de choisir les angles d’exploration et de générer des candidats.
- Lire references/evaluation-et-disponibilite.md avant de classer une shortlist ou de déclarer un candidat disponible.
- Lire references/structure-du-livrable.md pour produire le dossier final.
Workflow
1. Cadrer le projet
Relever ce qui est connu : offre, problème traité, publics, marché, zone géographique, langues, ambition, concurrence, origine du projet, idées de noms, préférences, interdits, budget d’acquisition éventuel et extensions ou plateformes prioritaires.
Demander uniquement les informations manquantes qui changent réellement l’orientation. Si le client ne peut pas répondre, formuler des hypothèses explicites et indiquer ce qui devra être validé.
2. Rechercher le contexte
Étudier le secteur, les conventions de naming, les concurrents directs et indirects, les associations sémantiques, les langues concernées et les références culturelles utiles. Distinguer les faits trouvés, les interprétations et les informations données par le client.
Utiliser des sources actuelles et fiables. Citer les sources dans le livrable lorsque la recherche externe influence une décision. Ne jamais inventer l’étymologie, la traduction ou la portée culturelle d’un mot.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 102 lines · 137 tokens per session scan A 928f82d16271
balise-brand-naming is a skill published in the GitHub repository mrstev3n/balise-skills (11 stars, last pushed 23d ago), licensed Apache-2.0. It adds 137 tokens to every session and 1,665 once invoked, about $0.0007 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
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.