run-scripts

run-scripts is a skill for Claude Code, Codex from marcellourbani/vscode_abap_remote_fs. It costs 81 tokens per session (6,305 once invoked), scanned A, original, MIT.

A procedure for executing SAP UI test cases with Playwright and generating DOCX evidence. It rediscovers the test folder, programs, specifications, test data, prepared data, and target SAP system before running selected cases.

In plain words
What is it for?
Use it to run named SAP test cases, execute linked stages across multiple SAP connections in order, produce evidence, and investigate test failures.
Why use it?
It makes sure required preparation steps are present and helps diagnose failures when a test script does not run correctly.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/marcellourbani/vscode_abap_remote_fs/run-scripts
Any agent
npx skills add marcellourbani/vscode_abap_remote_fs --skill run-scripts
Clone the repo
git clone --depth 1 https://github.com/marcellourbani/vscode_abap_remote_fs

Made for: Claude Code, Codex.

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.

agentmods badge for run-scripts

README.md
[![agentmods](https://agentmods.dev/badge/skills/marcellourbani/vscode_abap_remote_fs/run-scripts.svg)](https://agentmods.dev/skills/marcellourbani/vscode_abap_remote_fs/run-scripts)
Your own site
<a href="https://agentmods.dev/skills/marcellourbani/vscode_abap_remote_fs/run-scripts"><img src="https://agentmods.dev/badge/skills/marcellourbani/vscode_abap_remote_fs/run-scripts.svg" alt="Measured on agentmods" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,305 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00081 $0.06305
Opus 5 $0.00041 $0.03152
Sonnet 5 $0.00016 $0.01261
Haiku 4.5 $0.00008 $0.00630

Measured 5d ago against content hash b838fab04cc0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

run-scripts 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 5d 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.

client/media/skills/testing/run-scripts/SKILL.md · 229 lines

How it starts

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

Run Scripts — Phase 7 (of 7)

If selected cases are linked stages across SAP connections, load multi-system-workflows alongside this skill and execute separate connection-specific tool calls in stage order. Never put dependent stages in one parallel invocation.

Phase order: analyze-and-plan (1) → explore-ui (2) → design-cases (3) → define-data (4) → prepare-data (5) → build-scripts (6) → run-scripts (7).

For bounded, self-contained support work, use sap-task-helper with explicit inputs, allowed writes, and an output contract.

Tool availability (read this if a tool seems missing)

Naming: when these docs say call X, X is a tool (you invoke it and get a result); delegate to / invoke X is an agent (a subagent you launch); load / follow X is a skill (a procedure you read). A name without a verb: see the overview's "Skills, tools, and agents" list.

The editor may hide tools until searched for, and this is exactly where it bites: abapfs_run_playwright_tests is frequently NOT in the default active toolset, and smaller models fail to find it and waste turns trying run_in_terminal/runTests instead. Before Step 0, make sure abapfs_run_playwright_tests, abapfs_get_test_folder, abapfs_get_connected_systems, abapfs_check_test_data, and abapfs_build_evidence_report are available; if any is missing, search your available tools for it by name. Never use VS Code's generic runTests tool for SAP specs — it expects Vitest/Jest and returns "No tests found" for Playwright specs. If abapfs_run_playwright_tests cannot be found after searching, tell the user rather than improvising.

The abapfs_run_playwright_tests prerequisite gate

abapfs_run_playwright_tests is a GATED tool: it refuses to run unless you pass the mandatory prerequisiteConfirmation field. Only pass it after you have completed Step 0 (artifacts present AND abapfs_check_test_data clean for the selected cases). The exact text to pass is: I verified all upstream phase gates and test data readiness for this program. It is valid only once that gate is genuinely complete; the run is rejected otherwise.

Read the full file on GitHub · 229 lines

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.

  1. 5d ago First seen · 229 lines · 81 tokens per session scan A b838fab04cc0

Subscribe to this mod's changes

run-scripts is a skill published in the GitHub repository marcellourbani/vscode_abap_remote_fs (381 stars, last pushed 6d ago), licensed MIT. It adds 81 tokens to every session and 6,305 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.

Related

Other skills, from other repositories

write-ui-tests

Creates UI tests for a GitHub issue and verifies they reproduce the bug. Iterates until tests actually fail (proving they catch the issue). Use when PR lacks tests or tests need to be created for an issue.

dotnet/maui · 48 tokens

run-integration-tests

Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.

dotnet/maui · 35 tokens

run-device-tests

Build and run .NET MAUI device tests locally with category filtering. Supports iOS, MacCatalyst, Android on macOS; Android, Windows on Windows. Use TestFilter to run specific test categories.

dotnet/maui · 46 tokens

write-e2e-cases

Use when adding or updating Rsdoctor end-to-end tests in e2e/cases/, including new feature coverage, bug reproduction, and regression prevention.

web-infra-dev/rsdoctor · 39 tokens

sap-sac-test-automation

SAP Analytics Cloud (SAC) automated testing skill for designing capability-gated browser discovery and deterministic Playwright test suites for SAC stories, dashboards, reports, planning workflows, comments, permissions, visual regression, and reusable QA automation. This skill should be used when building SAC…

secondsky/sap-skills · 151 tokens

sap-tcd-chain

Drives a complete headless O2C business-document chain — sales order → outbound delivery → goods issue → billing — over RFC BAPIs, so regression testing gets whole document flows, not isolated documents. Each step is created via its SAP write BAPI, committed (WAIT='X'), and VBFA-verified before the next step (VBTYPN…

sapdev-ai/sap-dev · 269 tokens