A test-automation framework that lets you write plain-text BDD scenarios in .story files instead of Java code. It supports web, REST, mobile, database and cloud testing through plugins.

Use it to create Vividus projects, configure test environments, add testing plugins, write data-driven stories, and run or debug test suites.

It provides ready-made test steps and configuration conventions, so you do not have to build test actions or guess the framework's syntax.

vividus — Skill for Claude Code by arozumenko

Install

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.

Any agent

npx skills add arozumenko/sdlc-skills --skill vividus

Clone the repo

git clone --depth 1 https://github.com/arozumenko/sdlc-skills

Made for: Claude Code.

Or install sdlc-skills, the plugin that ships this one along with the rest of its 53 skills.

Its marketplace also offers this one on its own, as the plugin vividus — /plugin install vividus after adding the marketplace above.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/vividus/github.svg)](https://agentmods.dev/skills/arozumenko/sdlc-skills/vividus)

Your own site

<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/vividus"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/vividus/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/vividus"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/vividus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,727 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00077	$0.04727
Opus 5	$0.00039	$0.02364
Sonnet 5	$0.00015	$0.00945
Haiku 4.5	$0.00008	$0.00473

Measured 10d ago against content hash f8a24c8d6f49, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

vividus 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 10d 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.

skills/vividus/SKILL.md · 348 lines

How it starts

The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vividus Test Automation

Vividus is a JBehave-based BDD framework. Tests are plain-text .story files using a strict, pre-built step library — authors compose tests by wording, not Java. Plugins extend the step library per domain (web, REST, mobile, DB, cloud).

This skill knows the framework's conventions, file layout, properties model, and step phrasings so you can scaffold projects, add plugins, author/edit stories without invented steps, and run/debug suites.

Decision tree — pick a path

User intent	Path
New project from scratch	Bootstrap a project
Add web/REST/mobile/DB/etc. capability	Add a plugin
Write or edit a `.story` file	Author a story; read `references/steps-cheatsheet.md`
Configure suites/profiles/environments	Read `references/configuration.md`
Set up data-driven tests / external tables	Read `references/variables-and-tables.md`
Run, filter, debug	Run tests
Test won't match / step not found / locator fails	Read `references/troubleshooting.md`
Pick a plugin / understand 47-plugin catalog	Read `references/plugins.md`

When in doubt, ground every step phrasing against the docs (https://docs.vividus.dev/vividus/latest/) or against ./gradlew printSteps output. Do not invent step phrases — Vividus matches steps by exact wording (with parameters). If a step doesn't match, it silently becomes a "pending" step at runtime.

Core concepts you must internalize

Tests are .story files under src/main/resources/story/.... Sections: Description:, Meta:, GivenStories:, Lifecycle:, Scenario:, Examples:. Steps start with Given/When/Then.
Step parameters use backticks `, not quotes. Example: Then `${name}` is equal to `Bob`. This is the #1 syntax error.
Variables: ${var} for read, <col> for ExamplesTable placeholders, #{expression(...)} for compile-time expressions (data generation, formatting).
Three orthogonal config axes: configuration.suites, configuration.profiles, configuration.environments. Each loads .properties files; first declared wins.
BOM-pinned versions: org.vividus:vividus-bom:<version> controls every plugin's version. Never override individual plugin versions.
JDK 21 (Temurin recommended). Older JDKs fail with cryptic errors.
Build system is a git submodule (vividus-build-system). Always git clone --recursive, or run git submodule update --init --recursive after a regular clone.

Read the full file on GitHub · 348 lines

Files

What ships with it

17 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.

Changes

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.

10d ago First seen · 348 lines · 77 tokens per session scan A f8a24c8d6f49

Subscribe to this mod's changes

vividus is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 4,727 once invoked, about $0.0004 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-30.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

vividus