Borrowing it
Nothing to install: this file belongs to prebid/salesagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/prebid/salesagent/main/.claude/skills/inspect-bdd-steps/SKILL.mdgit clone --depth 1 https://github.com/prebid/salesagentWrote 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/prebid/salesagent/inspect-bdd-steps)<a href="https://agentmods.dev/skills/prebid/salesagent/inspect-bdd-steps"><img src="https://agentmods.dev/badge/skills/prebid/salesagent/inspect-bdd-steps/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/prebid/salesagent/inspect-bdd-steps"><img src="https://agentmods.dev/badge/skills/prebid/salesagent/inspect-bdd-steps.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.00086 | $0.00539 |
| Opus 5.5 | $0.00034 | $0.00216 |
| Sonnet 5.5 | $0.00017 | $0.00108 |
| Haiku 4.5 | $0.00009 | $0.00054 |
Grade A, and why
inspect-bdd-steps 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
BDD Step Assertion Completeness Inspector
Inspects every BDD step function for semantic completeness: does the function body actually implement what the step text claims?
Usage
/inspect-bdd-steps
/inspect-bdd-steps --pass1-only
What It Does
- AST scan: Extracts all
@given/@when/@thendecorated functions fromtests/bdd/steps/ - Pass 1 (Sonnet triage): For each Then step, asks: "Is there a HIGH
chance this function does NOT implement what the step text claims?"
- PASS: Function plausibly implements its claim
- FLAG: Function likely doesn't (pass body, truthiness-only check, etc.)
- Pass 2 (Opus deep trace): For each FLAG, collects production context (schemas, error classes, harness code) and asks Opus to make an architectural judgment about what the correct assertion should be.
- Report: Writes
.claude/reports/bdd-step-audit-<date>.mdwith findings grouped by severity (MISSING > WEAK > COSMETIC).
Protocol
Run the inspection script:
python3 .claude/scripts/inspect_bdd_steps.py
Options:
--pass1-only— Skip Pass 2 deep trace (fast triage only)--steps-dir PATH— Override step definitions directory--output PATH— Override report output path--then-only— Only inspect Then steps (default: true)
Review the generated report and use findings to inform beads-58u (assertion mismatch fixes) or create new tasks.
When to Use
- After writing new BDD step definitions
- After modifying existing step assertions
- As a periodic audit (monthly or per-epic)
- Before closing BDD-related PRs
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 · 62 lines · 86 tokens per session scan A d017b0af7fde
inspect-bdd-steps is a skill published in the GitHub repository prebid/salesagent (39 stars, last pushed yesterday), licensed Apache-2.0. It adds 86 tokens to every session and 539 once invoked, about $0.0003 per session on Opus 5.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-09-01.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.