Agent skill

Measure Scenario Times

by Cybereason-Public in Cybereason-Public/owLSM

Adds temporary pytest-bdd timing hooks and writes debugscenariotimes.txt plus sorted step and scenario files.

GPL-2.0Auto-check passedTesting & QA

Install Measure Scenario Times

skills CLI
$ npx skills add Cybereason-Public/owLSM --skill measure-scenario-times -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Cybereason-Public/owLSM measure-scenario-times --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Cybereason-Public/owLSM.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/measure-scenario-times .claude/skills/measure-scenario-times && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
measure-scenario-times
GitHub stars
280
Token cost
~676 tokens
SKILL.md length
262 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
GPL-2.0

At a glance

Adds temporary pytest-bdd timing hooks and writes debugscenariotimes.txt plus sorted step and scenario files.

  • The user asks to measure scenario time
  • SKILL.md covers Hooks, Sorted files and Run the suite
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Linux automation tests are slow

What it does

Measure Scenario Times is an agent skill from Cybereason-Public/owLSM. Adds temporary pytest-bdd timing hooks and writes debugscenariotimes.txt plus sorted step and scenario files. Use when the user asks to measure scenario time, step time, or why K8s or Linux automation tests are slow.

Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Unit testing and Container orchestration. It works with Linux, pytest and Kubernetes. The repository describes itself as: Sigma Rules Engine inside the Linux Kernel using eBPF. Focusing on prevention capabilities. The licence is GPL-2.0.

When your agent uses it

  • The user asks to measure scenario time
  • Linux automation tests are slow

Example prompts

  • “/measure-scenario-times”

What it can do on your machine

Read from SKILL.md and the folder at commit 8e541af. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Measure Scenario Times loads about 676 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 262 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~676

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Cybereason-Public/owLSM at commit 8e541af, republished under its GPL-2.0 licence (© Cybereason-Public). 262 words, ~676 tokens.

Download SKILL.mdSave it as .claude/skills/measure-scenario-times/SKILL.md (or your agent's skills folder).
name
measure-scenario-times
description
Adds temporary pytest-bdd timing hooks and writes debug_scenario_times.txt plus sorted step and scenario files. Use when the user asks to measure scenario time, step time, or why K8s or Linux automation tests are slow.

Measure scenario times

The user names the suite: K8s (src/Tests/K8S_Automation) or Linux (src/Tests/Automation). Add the hooks only in that suite. Remove them when the user says measuring is done.

Hooks

In that suite's conftest.py, write ~/owLSM/debug_scenario_times.txt. One line per event. Overwrite the file at session start (write_text). Append every later line. Skip all of this when collectonly is set.

Clock: datetime.now().strftime("%H-%M-%S") → [HH-MM-SS]. Elapsed seconds, one decimal: (datetime.now() - start).total_seconds().

Store scenario_start_time and step_start_time on the suite global:

  • K8s: globals/global_objects.py (global_objects)
  • Linux: globals/system_related_globals.py (system_globals)
HookWhen to writeLine
pytest_sessionstartfirst line, before existing setup[HH-MM-SS] session start
pytest_bdd_before_scenariofirst line, then set scenario_start_time, then existing work[HH-MM-SS] before scenario: '{scenario.name}'
pytest_bdd_before_stepfirst line, then set step_start_time[HH-MM-SS] before step: '{step.name}'
pytest_bdd_after_steplast line[HH-MM-SS] {seconds} after step: '{step.name}'
pytest_bdd_after_scenariolast line, after existing cleanup[HH-MM-SS] {seconds} after scenario: '{scenario.name}'
pytest_sessionfinishlast line, after existing cleanup[HH-MM-SS] session end

{seconds} uses step_start_time or scenario_start_time. Quote names with single quotes. Writing before the existing before-scenario work keeps the gap before the first step in the log.

Sorted files

After the run, write these next to the log. Sort by the seconds field, largest first. Keep the original lines.

  • ~/owLSM/sorted_step_time.txt — lines containing after step:
  • ~/owLSM/sorted_scenario_time.txt — lines containing after scenario:

Run the suite

  • Kind: src/Tests/K8S_Automation/AGENTS.md. conftest.py creates and deletes the cluster.
  • OKE: from the repo root, kubernetes/oke/run_oke.sh. Extra args are passed to pytest. Set OWLSM_IMAGE_REPOSITORY and OWLSM_IMAGE_TAG. OWLSM_OKE_SKIP_NODE_POOL_RECYCLE=1 skips node-pool recycle when the pool is already fresh.
  • Linux: src/Tests/Automation/README.md. Run pytest as root from that directory.

Do not commit the timing hooks or the three txt files.

© Cybereason-Public, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/measure-scenario-times of Cybereason-Public/owLSM.

Open the folder on GitHubat commit 8e541af

Compare with similar skills

Measure Scenario Times next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Measure Scenario Times compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Measure Scenario Times this skillCybereason-Public/owLSM280—~676Automated safety check: PassGPL-2.0
Chart Testsastronomer/astronomer491—~3.2kAutomated safety check: PassCustom licence
Chart Testsastronomer/airflow-chart297—~2.8kAutomated safety check: PassCustom licence
NIC Testing Patternsnginx/kubernetes-ingress5.1k—~2.8kAutomated safety check: PassApache-2.0
Issue WriterNVIDIA/container-canary308—~1.1kAutomated safety check: PassApache-2.0
Functional Testsastronomer/astronomer491—~2.2kAutomated safety check: PassCustom licence

Similar skills

  • Chart Tests

    astronomer/astronomer

    A skill your agent uses when writing, editing, reviewing, or running Helm chart tests for the Astronomer APC repository.

    491 GitHub stars~3.2k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Chart Tests

    astronomer/airflow-chart

    A skill your agent uses when writing, editing, reviewing, or running Helm chart tests for the Astronomer airflow-chart repository.

    297 GitHub stars~2.8k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed
  • NIC Testing Patterns

    nginx/kubernetes-ingress

    Testing conventions for the NGINX Ingress Controller repo: Go table-driven tests, mandatory snapshot regeneration, Helm tests and Python pytest integration tests.

    5.1k GitHub stars~2.8k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Issue Writer

    NVIDIA/container-canary

    Official

    Draft and revise concise, human-focused GitHub issues for pytest-kind-ng.

    308 GitHub stars~1.1k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Functional Tests

    astronomer/astronomer

    A skill your agent uses when writing, editing, reviewing, or running functional (end-to-end) tests for the Astronomer APC repository.

    491 GitHub stars~2.2k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • Backend Testing

    biersoeckli/QuickStack

    Create and review QuickStack backend unit and integration tests using the project's Vitest, Prisma, SQLite, and k3s conventions.

    361 GitHub stars~670 tokensUpdated yesterday
    Testing & QAAuto-check passed

More from Cybereason-Public/owLSM

All 9 skills in this repo
  • K8s Security Policies

    Cybereason-Public/owLSM

    Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.

    280 GitHub starsUsed in 12 repos~2k tokens
    Auto-check passed
  • Helm Chart Scaffolding

    Cybereason-Public/owLSM

    Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.

    280 GitHub starsUsed in 13 repos~381 tokens
    Auto-check passed
  • Kubernetes Architect

    Cybereason-Public/owLSM

    Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration.

    280 GitHub starsUsed in 9 repos~2.6k tokens
    Auto-check passed
  • K8s Manifest Generator

    Cybereason-Public/owLSM

    Step-by-step guidance for creating production-ready Kubernetes manifests including Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims.

    280 GitHub starsUsed in 12 repos~433 tokens
    Auto-check passed
  • Add Gitmcp

    Cybereason-Public/owLSM

    Adds a GitMCP URL for a GitHub repository to the project's MCP configuration (.cursor/mcp.json).

    280 GitHub stars~919 tokensUpdated 3 days ago
    Auto-check passed
  • GitHub Issues

    Cybereason-Public/owLSM

    Manage GitHub issues - create, edit, close, comment, assign, and delegate to Copilot.

    280 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Measure Scenario Times

What does Measure Scenario Times do?

Adds temporary pytest-bdd timing hooks and writes debugscenariotimes.txt plus sorted step and scenario files. Measure Scenario Times is an agent skill from Cybereason-Public/owLSM.txt plus sorted step and scenario files.

When should I use Measure Scenario Times?

Measure Scenario Times fits situations like: the user asks to measure scenario time; linux automation tests are slow.

How do I install Measure Scenario Times in Claude Code?

Run `npx skills add Cybereason-Public/owLSM --skill measure-scenario-times -a claude-code`. Or copy the skill folder (.cursor/skills/measure-scenario-times in Cybereason-Public/owLSM) into .claude/skills/measure-scenario-times in your project. Claude Code loads it when a task matches its description.

How do I install Measure Scenario Times in Codex?

Run `npx skills add Cybereason-Public/owLSM --skill measure-scenario-times -a codex`. Or copy the skill folder (.cursor/skills/measure-scenario-times in Cybereason-Public/owLSM) into .agents/skills/measure-scenario-times in your project. Codex loads it when a task matches its description.

Can I use Measure Scenario Times in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Cybereason-Public/owLSM --skill measure-scenario-times -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/measure-scenario-times, .gemini/skills/measure-scenario-times, .github/skills/measure-scenario-times and .opencode/skills/measure-scenario-times in your project.

What does Measure Scenario Times need to run?

SKILL.md names no scripts, command-line tools or credentials: Measure Scenario Times is instructions for the agent only.

Does Measure Scenario Times access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Measure Scenario Times safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Measure Scenario Times use?

Measure Scenario Times is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Measure Scenario Times use?

About 676 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Measure Scenario Times?

Skills that share tags, products or a category with Measure Scenario Times: Chart Tests (astronomer/astronomer, 491 stars), Chart Tests (astronomer/airflow-chart, 297 stars), NIC Testing Patterns (nginx/kubernetes-ingress, 5.1k stars) and Issue Writer (NVIDIA/container-canary, 308 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Measure Scenario Times?

Cybereason-Public (a GitHub organization) maintains it in Cybereason-Public/owLSM, which has 280 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.

Source: Cybereason-Public/owLSM on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.