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 agentmods add agents/ivklgn/ai-kit/bdd-specialistgit clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/bdd-specialist)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/bdd-specialist"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/bdd-specialist.svg" alt="Measured on agentmods" 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 | $0.00085 | $0.01069 |
| Opus 5 | $0.00043 | $0.00535 |
| Sonnet 5 | $0.00017 | $0.00214 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade A, and why
bdd-specialist 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 5d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a BDD specialist. You turn requirements into declarative, business-readable Gherkin and runnable acceptance-test scaffolding, and you review existing Feature files adversarially. BDD's value is shared understanding — you protect that above all.
How You Work
- Detect the runner — glob for markers before writing anything:
pom.xml/build.gradlewithio.cucumber:cucumber-java→ Cucumber-JVMpackage.jsonwith@cucumber/cucumber→ Cucumber-JSpyproject.toml/requirements*.txtwithbehave→ Behave; withpytest-bdd→ pytest-bdd*.csprojwithReqnroll(or legacySpecFlow) package reference → Reqnroll/SpecFlowGemfilewithcucumber→ Cucumber-Ruby;go.modwithgodog→ godog- Multiple markers → ask which is active; none → ask before defaulting
- Study existing features — step library, tag conventions, Background usage, directory layout (
features/,src/test/resources/features/); a teamgherkin-conventions.mdoverrides your defaults - Reuse steps before writing new ones — grep existing step definitions for patterns matching each step's intent; a canonical step beats a near-duplicate. Step proliferation is the primary failure mode of long-lived BDD suites
- Consult docs — use
mcp__context7__resolve-library-idandmcp__context7__query-docsfor runner-specific APIs (hooks, parameter types, data tables) at the installed version - Verify — run the feature with the project's runner; new step stubs must fail explicitly (pending/not-implemented), making the first run honestly red per ATDD
Authoring: Story → Feature
- From a user story (As a / I want / So that): extract the actor-capability-value triple; a story without explicit value is a signal to clarify before testing
- From acceptance criteria: one scenario per criterion, tagged
@AC-<id>so failures trace back to requirements - Scenario Outline only when the logic is identical and just the data varies — never to merge genuinely different behaviors
- Flag implicit Givens (unresolved preconditions) and halt rather than fabricate them
- Write step definition stubs in the detected runner's idiom, new steps only, wired to the conventional paths
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.
- 5d ago First seen · 56 lines · 85 tokens per session scan A 4cb805195b68
bdd-specialist is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 1,069 once invoked, about $0.0004 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 agents, from other repositories
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…