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 szampier/skills --skill edps-workflowgit clone --depth 1 https://github.com/szampier/skillsWrote 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/szampier/skills/edps-workflow)<a href="https://agentmods.dev/skills/szampier/skills/edps-workflow"><img src="https://agentmods.dev/badge/skills/szampier/skills/edps-workflow.svg" alt="Measured on agentmods" 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.00062 | $0.02193 |
| Opus 5 | $0.00031 | $0.01097 |
| Sonnet 5 | $0.00012 | $0.00439 |
| Haiku 4.5 | $0.00006 | $0.00219 |
Grade A, and why
edps-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
edps-workflow
What is an EDPS workflow?
An EDPS workflow package is a set of Python files that tell the ESO Data Processing System how to classify, group, and process raw data with instrument pipeline recipes. The files follow strict naming conventions: <instrument>_wkf.py, _datasources.py, _classification.py, _rules.py, _keywords.py, _task_functions.py, and _parameters.yaml.
Quick start
Before editing, verify the workflow loads:
edps -lw # lists all registered workflows
edps -lt -w uves.uves_wkf # lists tasks in the UVES workflow (smoke-test)
edps -lt -w uves.uves_wkf -P 5001 # same, if EDPS runs on a non-default port
application.properties in ~/.edps/ must include a workflow_dir pointing to your working directory. Instrument subdirectories must exist (e.g. muse/muse_wkf.py).
Adding a new task (primary workflow)
Follow this checklist in order — each step depends on the previous.
1. Understand what exists
Read _wkf.py to see all current tasks and their dependency chain. Note:
- Which tasks produce outputs that your new task will use as calibration
- Which
data_sourceobjects are already defined in_datasources.py - The
PRODUCT_TYPEclassification rules already in_classification.py
2. Add a classification rule (if a new file type is introduced)
In _classification.py, add a rule for any new raw or product type:
from edps import classification_rule
new_type_class = classification_rule('NEW_TYPE', {
kwd.instrume: "INSTR",
kwd.dpr_catg: "CALIB",
kwd.dpr_type: "NEW_TYPE",
})
# For pipeline products (output of a previous recipe):
NEW_PRODUCT = classification_rule("NEW_PRODUCT", {kwd.instrume: "INSTR", kwd.pro_catg: "NEW_PRODUCT"})
3. Add a datasource (if a new input is needed)
In _datasources.py, define a datasource for the new raw input and import the classification rule:
from edps import data_source, RelativeTimeRange
from edps.generator.time_range import UNLIMITED, ONE_DAY
raw_new = (data_source("NEW_TYPE")
.with_classification_rule(new_type_class)
.with_min_group_size(3)
.with_setup_keywords(setup) # list of FITS keywords defining the setup
.with_grouping_keywords(grouping) # how to group files into batches
.with_match_keywords([kwd.arm, kwd.ins_slit], time_range=ONE_DAY, level=0)
.with_match_keywords([kwd.arm, kwd.ins_slit], time_range=UNLIMITED, level=3)
.build())
What ships with it
12 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.
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.
- 7d ago First seen · 172 lines · 62 tokens per session scan A 0d56dddcbb64
edps-workflow is a skill published in the GitHub repository szampier/skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 2,193 once invoked, about $0.0003 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-31.
Other skills, from other repositories
jupyter-notebook
Iterative Python via live Jupyter kernel (hamelnb).
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
bioservices
Unified Python interface to 40+ bioinformatics services. Use when querying multiple databases (UniProt, KEGG, ChEMBL, Reactome) in a single workflow with consistent API. Best for cross-database analysis, ID mapping across services. For quick single-database lookups use gget; for sequence/file manipulation use…
pennylane
Hardware-agnostic quantum ML framework with automatic differentiation. Use when training quantum circuits via gradients, building hybrid quantum-classical models, or needing device portability across IBM/Google/Rigetti/IonQ. Best for variational algorithms (VQE, QAOA), quantum neural networks, and integration with…
cuopt-numerical-optimization-api
LP, MILP, and QP (beta) with cuOpt — Python, C, and CLI. Use when the user is solving LP, MILP, or QP with any cuOpt interface.
rocm-kernels
Provides guidance for writing and benchmarking optimized Triton kernels for AMD GPUs (MI355X, R9700) on ROCm, targeting HuggingFace diffusers (LTX-Video, SD3, FLUX) and transformers. Core kernels: RMSNorm, RoPE 3D, GEGLU, AdaLN. Includes XCD swizzle, autotune, diffusers integration patterns, and LTX-Video pipeline…