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/ivangrynenko/cursorrulesWrote 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/commands/ivangrynenko/cursorrules/behat-drevops)<a href="https://agentmods.dev/commands/ivangrynenko/cursorrules/behat-drevops"><img src="https://agentmods.dev/badge/commands/ivangrynenko/cursorrules/behat-drevops/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/commands/ivangrynenko/cursorrules/behat-drevops"><img src="https://agentmods.dev/badge/commands/ivangrynenko/cursorrules/behat-drevops.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.02620 |
| Opus 5.5 | $0.00000 | $0.01048 |
| Sonnet 5.5 | $0.00000 | $0.00524 |
| Haiku 4.5 | $0.00000 | $0.00262 |
Grade A, and why
behat-drevops 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.
How it starts
The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Command: Behat DrevOps
Command Usage
/behat-drevops <task>
Treat <task> as the description of the Behat scenario the user wants. The remainder of this guide explains how to fulfil that request.
Role definition
You are behat test writer, implement the test requested as {$ARGUMENT}
DrevOps Behat Steps Integration
For Drupal projects using the drevops/behat-steps library, which provides comprehensive Behat step definitions. When available in vendor/drevops/behat-steps/, use these pre-built steps.
Available Behat Traits from DrevOps
When writing custom Behat tests, check for these available traits:
Common Traits
ContentTrait- Content management stepsFieldTrait- Field interaction stepsFileTrait- File handling stepsPathTrait- Path navigation stepsSearchApiTrait- Search API testing stepsTaxonomyTrait- Taxonomy term stepsWaitTrait- Wait conditions stepsWatchdogTrait- Watchdog/logging steps
Additional Available Traits
BigPipeTrait- BigPipe functionality testingBlockContentTrait- Block content managementBlockTrait- Block placement and configurationCookieTrait- Cookie manipulationDateTrait- Date field handlingDraggableViewsTrait- Draggable views testingEckTrait- Entity Construction Kit supportElementTrait- DOM element interactionsEmailTrait- Email testing capabilitiesFileDownloadTrait- File download verificationJsTrait- JavaScript executionKeyboardTrait- Keyboard interactionLinkTrait- Link verificationMediaTrait- Media entity handlingMenuTrait- Menu system testingMetaTagTrait- Meta tag verificationOverrideTrait- Override functionalityParagraphsTrait- Paragraphs field testingResponseTrait- HTTP response assertionsRoleTrait- User role managementSelectTrait- Select field interactionsTestmodeTrait- Test mode utilitiesUserTrait- User managementVisibilityTrait- Element visibility checksWysiwygTrait- WYSIWYG editor testing
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 · 379 lines · 0 tokens per session scan A 4763b26fed2e
behat-drevops is a command published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,620 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-30.
Other commands, from other repositories
e2e
Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.
test-coverage
Analyze test coverage and generate missing tests.
test-run
Run E2E tests with qa-use CLI.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
record
Record the browser while validating a flow, then judge it against a rubric.
maestro-selectors-instructions
Guide to using Maestro selectors for targeting UI elements in tests.