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 Decathlon/tzatziki --skill java-tests-tzatzikigit clone --depth 1 https://github.com/Decathlon/tzatzikiWrote 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/decathlon/tzatziki/java-tests-tzatziki)<a href="https://agentmods.dev/skills/decathlon/tzatziki/java-tests-tzatziki"><img src="https://agentmods.dev/badge/skills/decathlon/tzatziki/java-tests-tzatziki/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/decathlon/tzatziki/java-tests-tzatziki"><img src="https://agentmods.dev/badge/skills/decathlon/tzatziki/java-tests-tzatziki.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.00119 | $0.04433 |
| Opus 5.5 | $0.00048 | $0.01773 |
| Sonnet 5.5 | $0.00024 | $0.00887 |
| Haiku 4.5 | $0.00012 | $0.00443 |
Grade A, and why
java-tests-tzatziki 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 6d 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.
This is a copy
91% identical to add-cucumber-tests — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BDD Test Generation with Tzatziki
Generate valid Cucumber .feature files from a user's functional specification, using Tzatziki's
step definition library as the source of truth for legal step patterns.
Principles
These explain the reasoning behind the workflow — understanding them helps you handle edge cases the workflow doesn't explicitly cover.
-
Steps come from code, not imagination. Tzatziki provides hundreds of pre-built
@Given/@When/@Thenpatterns in its*Steps.javafiles. Inventing step text that doesn't match a real definition producesUndefinedStepExceptionat runtime. Per-module reference files inreferences/steps-*.mdcontain every legal step pattern — read the relevant ones before writing any scenario.⚠️ Never paraphrase or improvise step keywords. Many step patterns use regex constants like
COMPARING_WITHthat expand to a small fixed set of keywords (e.g.,""empty," exactly"," at least"," only"). Do not substitute natural-language synonyms such as"containing","including","matching", or any other word that "sounds right" — if the word does not appear in the@Given/@When/@Thenannotation regex, the step will be undefined at runtime. When in doubt, re-read the Java source inreferences/steps-*.mdrather than guessing. -
Verify the environment before writing tests. Run at least one existing Cucumber test in the target module before creating new feature files. This catches missing dependencies, broken bootstrap, or misconfigured runners early — before you've invested effort in writing scenarios that can't execute. If no test exists yet, create the minimal bootstrap first and confirm it discovers at least one scenario.
-
YAML by default for structured data. Tzatziki scenarios are most readable when request bodies, database fixtures, Kafka payloads, and expected results use
"""ymldoc strings. Fall back to Gherkin tables for naturally tabular data, or raw JSON only when the contract requires it.
What ships with it
13 files 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.
- references/bootstrap-templates.md 2.5 KB
- references/cli-execution.md 4.0 KB
- references/steps-core.md 73 KB
- references/steps-http.md 97 KB
- references/steps-jackson3.md 13 KB
- references/steps-kafka.md 30 KB
- references/steps-logback.md 11 KB
- references/steps-mcp.md 28 KB
- references/steps-opensearch.md 11 KB
- references/steps-spring-jpa.md 32 KB
- references/steps-spring-kafka.md 32 KB
- references/steps-spring-mongodb.md 13 KB
- references/steps-spring.md 9.1 KB
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.
- 6d ago First seen · 321 lines · 119 tokens per session scan A 476920904cf6
java-tests-tzatziki is a skill published in the GitHub repository Decathlon/tzatziki (88 stars, last pushed 7d ago), licensed Apache-2.0. It adds 119 tokens to every session and 4,433 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to add-cucumber-tests, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
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.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.