Real Skill packageSource verifiedClawHub registry

instagram-scraper

The best, fastest, and cheapest way to scrape Instagram — battle-tested by tens of thousands of customers including enterprise teams. Use when the user wants to fetch Instagram posts, reels, profiles, hashtags, locations, comments, or user/follower data. Five specialized actors cover every Instagram

Identity and source

Publisher attributionAPI Dojoregistry owner unverified by skillvetai
Functional categorySupport, Ecommerce & Customer Opsautomatically inferred · 58% rule confidence
Package forminstruction bundle2 recorded files
Canonical sourceClawHub registryclawhub:apidojo-io:instagram-scraper
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 9/3/2026.claude/skills/instagram-scraper

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 9/3/2026.agents/skills/instagram-scraper

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 9/3/2026skills/instagram-scraper

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @apidojo-io/instagram-scraper
clawhub inspect @apidojo-io/instagram-scraper --version 1.0.0

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
1 / 1 inspected as text
Checked
9/3/2026, 4:23:02 AM
Scanner
0.1.3
Policy
1.0.3
1 inferred permission indicators
  • network access — automatically inferred
4 dependency and API indicators
  • api: api.apify.com
  • api: apify.com
  • api: console.apify.com
  • api: www.instagram.com
External clawhub result: suspicious

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
9/3/2026, 6:34:23 AM
Release binding
Matches this record
  • vt: clean
  • skillspector: suspicious
  • llm: suspicious

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:d51e76f398d2a6c418250ba2fd9256bcd5c8a3e47495117a39f5fec77af873fd
Show up to 2 recorded paths
  • skill-card.md
  • SKILL.md

Source changelog

- Major overhaul: Replaced browser-based Python/Playwright implementation with API-based approach using Apify actors for Instagram data extraction. - Now covers all Instagram data types (posts, reels, profiles, hashtags, locations, comments, followers) via specialized API actors. - No code or proxy setup needed; usage now requires Apify paid account and API token. - Updated and simplified usage instructions for both quick sync and large async runs. - Old documentation and feature list removed to reflect new API actor-based scraping workflow.

Release security diff

mediumCompared fixed releases 0.1.0 and 1.0.0; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • file surface changed
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

0.1.09/2/2026sha256:4f3d1436f949dbd3652327d75c4496b35f9455062c6ec17a1c8a522e8e91e886