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 skills/pramoddutta/qaskills/behave-bdd-testingnpx skills add PramodDutta/qaskills --skill behave-bdd-testinggit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/behave-bdd-testing)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/behave-bdd-testing"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/behave-bdd-testing.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.1 | $0.00036 | $0.04261 |
| Opus 5 | $0.00018 | $0.02131 |
| Sonnet 5 | $0.00007 | $0.00852 |
| Haiku 4.5 | $0.00004 | $0.00426 |
Grade B, and why
Behave BDD Testing scanned grade B with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt-get update Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get(f"{context.api_url}/health") How it starts
The opening of the file, as written. The whole thing — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behave BDD Testing
You are an expert QA engineer specializing in Behave, the Python BDD testing framework. When the user asks you to write, review, debug, or set up Behave tests, follow these detailed instructions. You understand the Behave ecosystem deeply including Gherkin feature files, step definitions, environment hooks, context management, fixtures, tag-based filtering, and integration with Selenium, Requests, and other Python libraries.
Core Principles
- Business-Readable Scenarios — Write Gherkin scenarios in plain language that stakeholders can understand. Avoid technical implementation details in feature files.
- Reusable Step Definitions — Design steps to be generic and composable. Use parameterized steps with regex patterns to maximize reuse across features.
- Context as Communication — Use
contextobject to pass data between steps cleanly. Store page objects, API clients, and test data on context in hooks. - Environment Hooks for Lifecycle — Manage browser setup, database seeding, and cleanup in
environment.pyhooks rather than in step definitions. - Tag-Based Organization — Use tags (
@smoke,@regression,@wip) to organize and filter test execution. Tags drive fixture selection and reporting. - Page Object Pattern — Separate page interactions from step logic. Step definitions call page object methods; page objects encapsulate selectors and browser interactions.
- Fail Fast with Clarity — Assertions should produce clear, descriptive failure messages. Capture screenshots and logs on failure for debugging.
Project Structure
project-root/
├── features/
│ ├── auth/
│ │ ├── login.feature
│ │ ├── signup.feature
│ │ └── password_reset.feature
│ ├── shopping/
│ │ ├── cart.feature
│ │ └── checkout.feature
│ ├── steps/
│ │ ├── auth_steps.py
│ │ ├── shopping_steps.py
│ │ ├── navigation_steps.py
│ │ └── common_steps.py
│ ├── pages/
│ │ ├── base_page.py
│ │ ├── login_page.py
│ │ ├── dashboard_page.py
│ │ └── cart_page.py
│ ├── fixtures/
│ │ ├── browser.py
│ │ ├── database.py
│ │ └── api_client.py
│ └── environment.py
├── reports/
│ ├── screenshots/
│ └── allure-results/
├── config/
│ ├── dev.ini
│ ├── staging.ini
│ └── prod.ini
├── behave.ini
├── requirements.txt
└── pytest.ini
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.
- 2d ago First seen · 517 lines · 36 tokens per session scan B 3de6dee4d7cb
Behave BDD Testing is a skill published in the GitHub repository PramodDutta/qaskills (217 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 4,261 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
pennylane
Hardware-agnostic quantum ML framework with automatic differentiation. Use when training quantum circuits via gradients, building hybrid quantum-classical models, or needing device portability across IBM/Google/Rigetti/IonQ. Best for variational algorithms (VQE, QAOA), quantum neural networks, and integration with…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
typing-exclusion-worker
Python typing exclusion worker: remove assigned mypy exclusion modules in small scoped batches, fix typing issues, run validation, and produce a structured completion summary. Use when running parallel typing-debt workers or when asked to remove modules from pyproject mypy exclusion overrides.
python
Python development with ruff, mypy, pytest - TDD and type safety.
splitting-oversized-modules
Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior. Use on a request to split / break up / decompose a god module or move functions out of one, once a human has agreed to…
test-python-binding
Build and test the NeMo Relay Python binding and worker plugin SDK; use for python/nemorelay, python/plugin, or crates/python changes.