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 broadinstitute/fiss-mcp --skill extract-workflow-datagit clone --depth 1 https://github.com/broadinstitute/fiss-mcpWrote 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/broadinstitute/fiss-mcp/extract-workflow-data)<a href="https://agentmods.dev/skills/broadinstitute/fiss-mcp/extract-workflow-data"><img src="https://agentmods.dev/badge/skills/broadinstitute/fiss-mcp/extract-workflow-data.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.00033 | $0.00997 |
| Opus 5 | $0.00016 | $0.00498 |
| Sonnet 5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
extract-workflow-data 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 8d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extracting Workflow Data Efficiently
This skill teaches you how to extract specific data from Cromwell workflow metadata without loading the entire 100K+ token metadata blob into your context.
Recommended Usage Pattern
Step 1: Start with Summary Mode (Default)
get_job_metadata(workspace_namespace, workspace_name, submission_id, workflow_id)
Summary mode returns a structured, context-efficient summary (~1-2K tokens) including:
- Workflow status and timing
- Task counts by status
- Failed task details with errors
- Execution summary
This gives you the lay of the land without context exhaustion.
Step 2: Extract Specific Data with Extract Mode
Use semantic parameters to get exactly what you need:
Get a Specific Task Output
get_job_metadata(
workspace_namespace, workspace_name, submission_id, workflow_id,
mode="extract",
task_name="illumina_demux",
output_name="commonBarcodes"
)
Get Output from a Specific Shard
For scattered tasks with multiple shards:
get_job_metadata(
workspace_namespace, workspace_name, submission_id, workflow_id,
mode="extract",
task_name="align_reads",
shard_index=5,
output_name="aligned_bam"
)
Get Runtime Attributes for All Tasks
Use wildcards with dot-path notation:
get_job_metadata(
workspace_namespace, workspace_name, submission_id, workflow_id,
mode="extract",
field_path="calls.*.runtimeAttributes"
)
This returns a dictionary mapping task names to their runtime attributes.
Dot-Path Syntax Reference
The field_path parameter supports flexible extraction using dot notation:
| Syntax | Meaning | Example |
|---|---|---|
key.subkey |
Nested access | calls.task1.outputs |
key[N] |
Array indexing | calls.task1[0].outputs |
key.* |
Wildcard (all keys) | calls.*.executionStatus |
Examples
# Get execution status of all tasks
field_path="calls.*.executionStatus"
# Get first shard's outputs for a specific task
field_path="calls.my_task[0].outputs"
# Get all runtime attributes
field_path="calls.*.runtimeAttributes"
# Get preemptible setting across all tasks
field_path="calls.*.runtimeAttributes.preemptible"
# Get backend status
field_path="calls.*[0].backendStatus"
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.
- 8d ago First seen · 153 lines · 33 tokens per session scan A d8c4898f7947
extract-workflow-data is a skill published in the GitHub repository broadinstitute/fiss-mcp (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 33 tokens to every session and 997 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-31.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
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.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
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.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…