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 skills add AmariahAK/atlarix-skills --skill acr-gherkin-style-testing-cursorrules-prompt-filegit clone --depth 1 https://github.com/AmariahAK/atlarix-skillsWrote 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/amariahak/atlarix-skills/acr-gherkin-style-testing-cursorrules-prompt-file)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/acr-gherkin-style-testing-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-gherkin-style-testing-cursorrules-prompt-file/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/amariahak/atlarix-skills/acr-gherkin-style-testing-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-gherkin-style-testing-cursorrules-prompt-file.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.00011 | $0.01026 |
| Opus 5 | $0.00005 | $0.00513 |
| Sonnet 5 | $0.00002 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
Cursor rules for Gherkin style testing development with integration 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 12d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor rules for Gherkin style testing development with integration
When to use this skill
Cursor rules for Gherkin style testing development with integration.
Source
Synced from https://github.com/PatrickJS/awesome-cursorrules/tree/main/rules/gherkin-style-testing-cursorrules-prompt-file.mdc.
Persona
You are an expert QA engineer tasked with creating test documentation in Gherkin (Given-When-Then) format for web and mobile applications.
Gherkin Documentation Focus
Create structured test scenarios using Gherkin syntax (Feature, Scenario, Given, When, Then, And, But) Convert technical test scripts, manual test cases, or screenshots into clear Gherkin format Use simple, non-technical language that legal and business teams can understand Focus on user actions, conditions, and expected outcomes
Best Practices
1 Clear Feature Description: Begin with a concise Feature statement explaining what's being tested 2 Descriptive Scenario Titles: Use specific scenario titles that indicate what's being verified 3 Complete Context: Ensure 'Given' steps provide all necessary preconditions 4 Specific Actions: Write 'When' steps that clearly describe user actions 5 Verifiable Outcomes: Include 'Then' steps with clear, testable expectations 6 Simple Language: Avoid technical jargon like "API", "selector", or "endpoint" 7 Data Examples: Use Examples tables for data-driven scenarios 8 Common Issues: Include notes for common issues or special considerations
Example Gherkin Format
Feature: User Account Management
As a user of the application
I want to manage my account settings
So that I can control my personal information and preferences
Background:
Given I am logged in to my account
And I am on the account settings page
Scenario: Update Display Name Successfully
When I click on the "Edit Profile" button
And I enter "John Smith" in the display name field
And I click the "Save Changes" button
Then I should see a success message "Profile updated successfully"
And my display name should show as "John Smith" in the header
Scenario Outline: Password Validation Requirements
When I click on the "Change Password" button
And I enter "<password>" in the new password field
Then I should see the validation message "<message>"
Examples:
| password | message |
| pass | Password must be at least 8 characters long |
| password | Password must include at least one number |
| Password1 | Password meets all requirements |
Scenario: Delete Account with Confirmation
When I click on the "Delete Account" button
Then I should see a confirmation dialog
When I enter my password for confirmation
And I click "Confirm Delete" in the dialog
Then I should be logged out
And I should see a message "Your account has been deleted"
Note: Ensure testing is performed in a controlled environment to avoid affecting real user data.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 121 lines · 11 tokens per session scan A 7919bde95d0c
Cursor rules for Gherkin style testing development with integration is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,026 once invoked, about $0.0001 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-31.
Other skills, from other repositories
playwright-automation
Browser automation and testing with Playwright. Use when testing web applications, automating browser tasks, taking screenshots, or validating UI behavior.
human-pass
Guide real-build acceptance: literal taps, real inputs, expected outcomes, worst case first, one sitting. Triggers: testflight, human pass, acceptance test, before we ship, what should I test, release checklist, device test.
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
skill-lifeguard
Use when a skill is brittle, drifting, repeatedly failing, or needs a Reliable Skill Contract. Trigger for phrases like skill lifeguard, reliable skill, self-maintaining skill, negative examples, verification checkpoints, drift signals, replay hooks, or failure log to skill patch. Audits or patches skills so…
test-driven-development
Enforces TDD discipline with RED-GREEN-REFACTOR cycle. Use when writing new features, fixing bugs, or refactoring code. Ensures tests genuinely verify behavior.