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 agentmods add skills/aws-samples/sample-healthomics-agentic-setup/skillnpx skills add aws-samples/sample-healthomics-agentic-setup --skill skillgit clone --depth 1 https://github.com/aws-samples/sample-healthomics-agentic-setupWrote 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/aws-samples/sample-healthomics-agentic-setup/skill)<a href="https://agentmods.dev/skills/aws-samples/sample-healthomics-agentic-setup/skill"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-healthomics-agentic-setup/skill.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 | $0.00053 | $0.00419 |
| Opus 5 | $0.00026 | $0.00210 |
| Sonnet 5 | $0.00011 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
aws-healthomics 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 4d 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.
The source is not reproduced here
Licensed MIT-0
The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
14 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.
- references/batch-runs.md 10 KB
- references/ecr-pull-through-cache.md 9.5 KB
- references/git-integration.md 7.3 KB
- references/healthomics-configuration.md 15 KB
- references/image-staging.md 13 KB
- references/migration-guide-for-nextflow.md 14 KB
- references/migration-guide-for-wdl.md 25 KB
- references/regional-capabilities.md 4.4 KB
- references/running-a-workflow.md 5.6 KB
- references/troubleshooting.md 4.9 KB
- references/vpc-connected-workflow-runs.md 7.1 KB
- references/vpc-setup.md 9.6 KB
- references/workflow-development.md 7.4 KB
- references/workflow-versioning.md 3.2 KB
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.
- 4d ago First seen · 40 lines · 53 tokens per session scan A 3ef38a180e92
aws-healthomics is a skill published in the GitHub repository aws-samples/sample-healthomics-agentic-setup (4 stars, last pushed 22d ago), licensed MIT-0. It adds 53 tokens to every session and 419 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
modal-compute
Run explicitly chosen research benchmark or replication jobs on Modal's serverless infrastructure. Use when a Feynman research workflow needs burst remote GPU compute and the Modal CLI is available.
remote-compute-ssh
Evaluate and use SSH Remote Compute before choosing where to run GPU, high-memory, parallel, batch, model-inference, bioinformatics, or other long-running scientific work; supports short remote commands and asynchronous jobs with automatic harvest and analysis.
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
remote-compute-ssh
Run Feynman research jobs on SSH, Slurm, or lab hosts. Use when a task needs remote host setup, job submission, log harvest, artifact sync, or GPU/cluster execution outside Modal.
remote-compute-modal
Dispatch Feynman research notebook or experiment jobs to Modal. Use when a task has explicitly chosen Modal for bounded cloud compute, GPU jobs, or reproducible remote execution.
runpod-compute
Provision and manage GPU pods on RunPod for explicitly chosen long-running research experiments. Use when a Feynman replication, benchmark, or dataset-heavy research run needs persistent GPU compute with SSH access.