develop-workflow

A procedure for designing and testing an OpenSDL workflow using a simulation manifest. A workflow is an ordered set of laboratory actions, while a simulation manifest describes a test environment without live equipment.

In plain words
What is it for?
Use it to build or revise simulated workflows, validate them, run representative JSON inputs, inspect failures, and export the resulting execution record.
Why use it?
It lets developers validate workflow inputs, dependencies, resources, retries, and outputs before running against real equipment. It also checks that each requested capability is connected to an approved adapter.

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/fl-sean03/opensdl/develop-workflow
Any agent
npx skills add fl-sean03/OpenSDL --skill develop-workflow
Clone the repo
git clone --depth 1 https://github.com/fl-sean03/OpenSDL

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 372 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.00035 $0.00372
Opus 5 $0.00017 $0.00186
Sonnet 5 $0.00007 $0.00074
Haiku 4.5 $0.00003 $0.00037

Measured yesterday against content hash 5936c44a7e10, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

develop-workflow 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 yesterday.

The scan reads SKILL.md. This mod also ships 1 executable file (run.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/develop-workflow/SKILL.md · 40 lines

What it actually says

Develop a simulated workflow

Inputs

  • simulation manifest path
  • workflow path
  • intended inputs, outputs, and failure behavior
  • representative JSON inputs

Procedure

  1. Read the manifest, capability contracts, and a nearby tested workflow.
  2. Confirm that spec.environment is simulation, review every enabled adapter, and trace every selected capability through its enabled binding to the intended adapter plugin.
  3. Define typed inputs, step dependencies, value bindings, resources, timeouts, retries, and outputs.
  4. Add or update focused workflow validation and execution tests.
  5. Run uv run --locked opensdl validate MANIFEST --workflow WORKFLOW.
  6. Run .agents/skills/develop-workflow/run.sh WORKFLOW MANIFEST 'INPUTS_JSON'. Before the runtime starts any adapter, the helper permits only the reviewed OpenSDL reference simulated-lab, local-compute, and human-task entry points and verifies every enabled plugin's module and distribution provenance. Qualify and review any addition before changing that allowlist.
  7. Inspect failure events when the run does not complete. Use debug-run for a persisted failure.
  8. Export the run when the user needs portable execution evidence.

Completion

The workflow validates, its tests pass, and a representative simulation run produces the expected outputs and persisted evidence.

Stop conditions

Stop before execution when the manifest environment is not simulation, a binding is missing or ambiguous, any enabled plugin is outside the reviewed simulation allowlist, or the workflow needs an operation that no typed capability provides.

Files

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.

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. yesterday First seen · 40 lines · 35 tokens per session scan A 5936c44a7e10

Subscribe to this mod's changes

develop-workflow is a skill published in the GitHub repository fl-sean03/OpenSDL (102 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 372 once invoked, about $0.0002 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.