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/b-fontaine/devoxx-2026Wrote 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/rules/b-fontaine/devoxx-2026/bdd-testing)<a href="https://agentmods.dev/rules/b-fontaine/devoxx-2026/bdd-testing"><img src="https://agentmods.dev/badge/rules/b-fontaine/devoxx-2026/bdd-testing/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/rules/b-fontaine/devoxx-2026/bdd-testing"><img src="https://agentmods.dev/badge/rules/b-fontaine/devoxx-2026/bdd-testing.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.00000 | $0.00298 |
| Opus 5.5 | $0.00000 | $0.00119 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
bdd-testing 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
Tests BDD — bdd_widget_test
Structure des fichiers .feature
Feature: Signalement d'anomalie
En tant qu'utilisateur de l'application
Je veux signaler une anomalie urbaine
Afin que la municipalité puisse intervenir
Scenario: Soumission réussie d'un signalement
Given l'utilisateur est sur la page de signalement
And le service de signalement est disponible
When l'utilisateur remplit le formulaire avec des données valides
And l'utilisateur soumet le signalement
Then un message de confirmation est affiché
And le signalement apparaît dans la liste
Conventions
- Un fichier .feature par fonctionnalité utilisateur
- Les steps Given/When/Then décrivent des comportements, pas des implémentations
- Les steps sont réutilisables entre scénarios
- Nommer les fichiers : snake_case matching le nom de la feature
Implémentation des steps
- Chaque step mappe vers une fonction Dart annotée
- Utiliser le WidgetTester pour les interactions UI
- Mocker les repositories dans les Given (jamais d'appel réseau réel)
- Les Then vérifient des widgets visibles, pas des états internes
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 · 36 lines · 0 tokens per session scan A eabec5cef44f
bdd-testing is a cursor rule published in the GitHub repository b-fontaine/devoxx-2026 (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 298 tokens. 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 cursor rules, from other repositories
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.