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 commands/ibrahimhajjaj/ig-dl/setupgit clone --depth 1 https://github.com/ibrahimhajjaj/ig-dlWrote 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/commands/ibrahimhajjaj/ig-dl/setup)<a href="https://agentmods.dev/commands/ibrahimhajjaj/ig-dl/setup"><img src="https://agentmods.dev/badge/commands/ibrahimhajjaj/ig-dl/setup.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.00019 | $0.00610 |
| Opus 5 | $0.00010 | $0.00305 |
| Sonnet 5 | $0.00004 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
setup 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 3d 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.
What it actually says
Walk the user through getting ig-dl ready to download Instagram content. Each step runs a real command via the Bash tool and reports its exit status before moving on.
Step 1 — Check the ig-dl binary is on PATH.
Run: which ig-dl && ig-dl --help | head -5
If not found, tell the user to install it: go install github.com/ibrahimhajjaj/ig-dl/cmd/ig-dl@latest. Stop.
Step 2 — Check gallery-dl and yt-dlp are on PATH.
Run: which gallery-dl yt-dlp
If either missing, suggest: brew install gallery-dl yt-dlp. Both are needed — gallery-dl for posts/stories/highlights/profiles, yt-dlp for reels.
Step 3 — Show current session status.
Run: ig-dl status
If "authed" already, skip to step 6. If "not authed", continue.
Step 4 — Ask the user to enable CDP in their browser.
Tell them exactly: "Open chrome://inspect/#remote-debugging (or edge://inspect/#remote-debugging) in your normal browser and toggle 'Allow remote debugging for this browser instance' ON. Make sure instagram.com is open in a tab and you're signed in there."
Wait for the user to confirm they did it.
Step 5 — Verify ig-dl sees the live browser.
Run: ig-dl browsers
If any entry shows [live], proceed. If every entry is [stale], tell the user the toggle didn't stick — they should try flipping it off and on again, or fall back to the companion extension path (step 7).
Step 6 — Capture the session.
Run: ig-dl login
Tell the user the browser will pop a permission dialog asking them to allow the remote debugging session — they must click Allow. On success, report "session captured from ".
Step 7 — If CDP didn't work, fall back to the companion extension.
Point the user at the repo's extension-companion/ directory, tell them to load it via chrome://extensions → Developer mode → Load unpacked, then click "Export session for CLI" in the extension's options page. Finally:
ig-dl login --import ~/Downloads/ig-dl-session.json
Final step — Confirm.
Run ig-dl status one more time and verify it reports authed (source=<browser or imported>, age=...s). If so, the setup is complete and the user can now run ig-dl <instagram-url> or use any of the ig_* MCP tools.
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.
- 3d ago First seen · 38 lines · 19 tokens per session scan A 756d25fa733b
setup is a command published in the GitHub repository ibrahimhajjaj/ig-dl (1 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 610 once invoked, about $0.0001 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 commands, from other repositories
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.
review-claims
Analyze patent claims for 35 USC 112(b) compliance - antecedent basis, definiteness, and claim structure.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-epo-formalities
Check patent application formalities for EPO compliance (Rules 42-49 EPC, EPO Guidelines Part A).
setup-patent-system
One-time setup for the patent creator system - downloads MPEP, builds search index, configures BigQuery.
typegen
Run Sanity TypeGen and troubleshoot type generation issues.