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 Ludovic33Fr/product-ai-toolbox --skill spec-from-briefgit clone --depth 1 https://github.com/Ludovic33Fr/product-ai-toolboxWrote 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/ludovic33fr/product-ai-toolbox/spec-from-brief)<a href="https://agentmods.dev/skills/ludovic33fr/product-ai-toolbox/spec-from-brief"><img src="https://agentmods.dev/badge/skills/ludovic33fr/product-ai-toolbox/spec-from-brief/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/ludovic33fr/product-ai-toolbox/spec-from-brief"><img src="https://agentmods.dev/badge/skills/ludovic33fr/product-ai-toolbox/spec-from-brief.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.00058 | $0.01142 |
| Opus 5 | $0.00029 | $0.00571 |
| Sonnet 5 | $0.00012 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
spec-from-brief 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 11d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-from-brief
Fiche éditoriale
Objectif. Transformer un brief flou en spec testable et exhaustive.
Entrées. Brief initial, base documentaire produit.
Sorties. User story INVEST, scénario nominal Given/When/Then, scénarios annexes, questions business non tranchées.
Cadence d'usage. À chaque nouvelle fonctionnalité spécifiée.
Mode opératoire
Quand m'invoquer
L'utilisateur me fournit un brief texte (mail, slack, paragraphe de roadmap) et demande de le transformer en spec, ou évoque un besoin de "passer du brief à la story", ou demande une spec INVEST.
Procédure
- Lire le brief en entier sans interpréter.
- Identifier l'utilisateur cible (rôle, contexte d'usage) ; si absent, l'inscrire en question business non tranchée.
- Identifier le bénéfice attendu ; si absent, idem.
- Reformuler en user story au format
En tant que <rôle>, je veux <action> afin de <bénéfice>. - Tester la story contre INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable). Pour chaque lettre, dire si elle est tenue ; sinon dire pourquoi.
- Construire le scénario nominal au format Given/When/Then.
- Lister les scénarios annexes : cas limites, états système particuliers, erreurs prévisibles. Chacun en Given/When/Then.
- Lister les questions business non tranchées : ambiguïtés du brief, choix de produit qui doivent être arbitrés avant la mise en chantier.
- Produire la sortie au format ci-dessous.
Format de sortie
# Spec — {titre court de la fonctionnalité}
## User story (INVEST)
> En tant que {rôle}, je veux {action} afin de {bénéfice}.
**Test INVEST**
- Independent : {oui / non — explication}
- Negotiable : {oui / non — explication}
- Valuable : {oui / non — explication}
- Estimable : {oui / non — explication}
- Small : {oui / non — explication}
- Testable : {oui / non — explication}
## Scénario nominal
Given {prérequis} When {action utilisateur} Then {résultat observable}
## Scénarios annexes
### {nom du scénario annexe 1}
Given ... When ... Then ...
### {nom du scénario annexe 2}
...
## Questions business non tranchées
1. {question}
2. {question}
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.
- 11d ago First seen · 132 lines · 58 tokens per session scan A d877a09a31e0
spec-from-brief is a skill published in the GitHub repository Ludovic33Fr/product-ai-toolbox (1 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 1,142 once invoked, about $0.0003 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
semble-setup
Project setup tools for semblecode semantic code search. Semantic search finds code by meaning or concept, rather than only matching exact words.
text-optimize
Optimizes text/docs for LLM token efficiency. Triggers - optimize, reduce tokens, compress, deep compress.
context-slim
A tool for shortening the instructions and saved information that an AI coding agent loads into its context, the text it uses to decide what to do.
md-to-pdf
Convert Markdown to PDF via reportlab or weasyprint engines. Triggers - pdf, md to pdf, markdown to pdf, generate pdf.
publish
A tool for publishing text, Markdown files, or websites to brewpage.app and receiving a web address for the published result.
agents
Creates, improves, syncs Codex subagents. Triggers: create agent, improve agent, sync agents, memory sync.