chipseq-pipeline

A bioinformatics workflow that processes raw DNA-sequencing files (FASTQ) from ChIP-seq experiments into DNA-binding sites (peaks) and signal tracks. ChIP-seq measures where a protein is attached to DNA; the workflow uses BWA-MEM, MACS2, and IDR.

In plain words
What is it for?
Use it to align reads, call protein-binding peaks, create signal tracks, and assess reproducibility in ENCODE-style ChIP-seq analysis.
Why use it?
It removes the need to assemble and run the main analysis steps by hand. It also applies IDR, a method for checking how consistently results agree between replicates.

Agent

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 agents/ammawla/encode-toolkit/chipseq-pipeline
Clone the repo
git clone --depth 1 https://github.com/ammawla/encode-toolkit
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 343 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00034 $0.00343
Opus 5 $0.00017 $0.00171
Sonnet 5 $0.00007 $0.00069
Haiku 4.5 $0.00003 $0.00034

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

Security

Grade A, and why

chipseq-pipeline 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 2d 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.

agents/chipseq-pipeline.md · 27 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2d ago First seen · 27 lines · 34 tokens per session scan A 5060a76659bf

Subscribe to this mod's changes

chipseq-pipeline is an agent published in the GitHub repository ammawla/encode-toolkit (24 stars, last pushed 1mo ago), licensed AGPL-3.0. It adds 34 tokens to every session and 343 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.